Allow to specify JMS username and password directly via properties in JMS
Transport.
------------------------------------------------------------------------------------
Key: AXIS2-4164
URL: https://issues.apache.org/jira/browse/AXIS2-4164
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: transports
Environment: Axis2 1.4.1 with Tibco EMS.
Reporter: Gabor Herr
Currently the JMS Transport on client side allows to specify username and
password for JNDI access via URL properties. In production environments
typically the JMS server also secured with username and password. There has
been an improvement to allow to specify JMS username passwords *indirectly* by
referring to corresponding JNDI entries
- transport.jms.ConnectionFactoryJNDIUser
- transport.jms.ConnectionFactoryJNDIPass
For a client only setup, where the JNDI content cannot be configured with these
indirect values, it would be useful to set these values directly via the URL.
The attached patch extends the current code to obtain these values from the
properties
- transport.jms.ConnectionFactoryUser
- transport.jms.ConnectionFactoryPass
If these are not set, it falls back to the previous JNDI values.
I hope, you could include this improvement into the next release.
--
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]
