[ 
https://issues.apache.org/jira/browse/QPIDJMS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPIDJMS-211:
-----------------------------------
    Description: 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.  (was: Currently the 
connection factory property handling in the JNDI bits uses "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 unecesary 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.)

> 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.1X.Y, 0.20.0
>
>
> 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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to