[
https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-2816.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Mark
I have applied the patch after a review - but not actual test. Please check the
next nightly build and let me know if you encounter any issues.
thanks again for the patch, and sorry for any delay to apply it
asankha
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0
> Reporter: Mark Badorrek
> Assignee: Asankha C. Perera
> Fix For: 1.3
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
