You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2016/10/03 16:10:20 UTC
[jira] [Updated] (QPIDJMS-211) make the JNDI connection factory
property handling more flexible
[ https://issues.apache.org/jira/browse/QPIDJMS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPIDJMS-211:
-----------------------------------
Fix Version/s: (was: 0.20.0)
> make the JNDI connection factory property handling more flexible
> ----------------------------------------------------------------
>
> Key: QPIDJMS-211
> URL: https://issues.apache.org/jira/browse/QPIDJMS-211
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.11.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.11.1
>
>
> Currently the connection factory property handling in the JNDI bits use "connectionfactory." (as used by our previous JMS clients), while most of the other config is camelCase. Similarly, some other clients use "connectionFactory." further adding to the chance of folks using it (deliberately or otherwise), leading to a bit of an unnecessary gotcha for users. Since this bit is just a prefix for scoping and detection, being flexible enough to treat these the same would be useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org