[
https://issues.apache.org/jira/browse/QPIDJMS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535757#comment-15535757
]
ASF subversion and git services commented on QPIDJMS-211:
---------------------------------------------------------
Commit c730c5319247a2c2f88f8e67976de6a92412d7dc in qpid-jms's branch
refs/heads/0.11.x from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=c730c53 ]
QPIDJMS-211: make the JNDI connection factory property handling a little more
flexible
(cherry picked from commit 5f46af2c1a2c48c0c9c8fcc8a1733a991e542ac8)
> 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: [email protected]
For additional commands, e-mail: [email protected]
