axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera" <asan...@wso2.com>
Subject Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Date Mon, 18 Jun 2007 12:01:34 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Mark<br>
<br>
Does WebSphere have a community edition (i.e. that does not require the
purchase of a license) that could be used to test this fix? <br>
<br>
asankha<br>
<br>
Mark Badorrek (JIRA) wrote:
<blockquote cite="mid21743782.1182162926102.JavaMail.jira@brutus"
 type="cite">
  <pre wrap="">     [ <a class="moz-txt-link-freetext" href="https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel">https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a>
]

Mark Badorrek updated AXIS2-2816:
---------------------------------

    Attachment: Axis2-websphereMQ-fix.zip

Can't test as I can't build Axis2 under maven at the moment.
If this is included in the nightly build I can run it through a websphereMQ test.

Current functionality remains unchanged; there is no logical or API modification.
The new functionality is only activated if the new parameters are present in the JNDI tree.



  </pre>
  <blockquote type="cite">
    <pre wrap="">JMS over WebsphereMQ doesn't support 'CLIENT' connections
---------------------------------------------------------

                Key: AXIS2-2816
                URL: <a class="moz-txt-link-freetext" href="https://issues.apache.org/jira/browse/AXIS2-2816">https://issues.apache.org/jira/browse/AXIS2-2816</a>
            Project: Axis 2.0 (Axis2)
         Issue Type: Bug
         Components: kernel
   Affects Versions: 1.2
        Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0
           Reporter: Mark Badorrek
        Attachments: Axis2-websphereMQ-fix.zip


Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
This is insufficient for WebspherMQ CLIENT connections, where the administrator must nominate
a particular userID and password per connectionfactory, resulting in the following call which
is unsupported in the Axis2 JMS code:
factory.createConnection(userID, password) 
The attached Axis2 JMS files contain the fix to allow the deployer to specify a nominated
userID and password through the standard Axis2 JNDI lookup mechanism.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message