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
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
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.