You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Gabor Herr (JIRA)" <ji...@apache.org> on 2008/12/03 16:21:44 UTC
[jira] Created: (AXIS2-4164) Allow to specify JMS username and
password directly via properties in JMS Transport.
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-4164) Allow to specify JMS username and
password directly via properties in JMS Transport.
Posted by "Gabor Herr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: 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
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-4164) Allow to specify JMS username and
password directly via properties in JMS Transport.
Posted by "Gabor Herr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Herr updated AXIS2-4164:
------------------------------
Attachment: axis141-jms-user.patch
> 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
> Attachments: axis141-jms-user.patch
>
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-4164) Allow to specify JMS username and
password directly via properties in JMS Transport.
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved AXIS2-4164.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.5
Assignee: Asankha C. Perera
Fixed with WS-Commons transport revision 724432
Introduced two new parameters
transport.jms.UserName
transport.jms.Password
> 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
> Assignee: Asankha C. Perera
> Fix For: 1.5
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-4164) Allow to specify JMS username and
password directly via properties in JMS Transport.
Posted by "Gabor Herr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Herr updated AXIS2-4164:
------------------------------
Description:
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.
was:
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.
Remaining Estimate: 0.5h
Original Estimate: 0.5h
> 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
> Attachments: axis141-jms-user.patch
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org