axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabor Herr (JIRA)" <>
Subject [jira] Updated: (AXIS2-4164) Allow to specify JMS username and password directly via properties in JMS Transport.
Date Wed, 03 Dec 2008 21:41:44 GMT


Gabor Herr updated AXIS2-4164:

    Attachment: axis141-jms-user.patch2

> Allow to specify JMS username and password directly via properties in JMS Transport.
> ------------------------------------------------------------------------------------
>                 Key: AXIS2-4164
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: transports
>         Environment: Axis2 1.4.1 with Tibco EMS.
>            Reporter: Gabor Herr
>         Attachments: axis141-jms-user.patch, axis141-jms-user.patch2
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
> 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.
> The second patch implements the same mechanism for JMSListener on the server side. In
this case the properties will be used from axis2.xml similar to the JNDI approach.
> I would appreciate, if 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:
For additional commands, e-mail:

View raw message