[ https://issues.apache.org/jira/browse/ARTEMIS-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039030#comment-16039030 ]
ASF subversion and git services commented on ARTEMIS-1207: ---------------------------------------------------------- Commit 754e9db5fdee3807758a4c2da14bc61e715d616f in activemq-artemis's branch refs/heads/master from [~michael.andre.pearce] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=754e9db ] ARTEMIS-1207: [Core JMS Client] Align order of when setClientId can be called with AcitveMQ5 and QPID Update ActiveMQConnection to change behaviour Add test to avoid regression. > [Core JMS Client] Align order of when setClientId can be called with > AcitveMQ5 and QPID > --------------------------------------------------------------------------------------- > > Key: ARTEMIS-1207 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1207 > Project: ActiveMQ Artemis > Issue Type: Bug > Reporter: Michael Andre Pearce > > There is a difference in behaviour of when it is valid to be able to set > clientId though it seems the behaviour isn't clear in JMS spec, where QPID > and ActiveMQ5 allow you to set an exception listener first, where as > currently Artemis requires the very first call to setClientId if you wish to > set it. > As discussed will create and align the clients so even so not detailed in > spec, a user of ActiveMQ5 client or QPID client can expect the same behaviour. -- This message was sent by Atlassian JIRA (v6.3.15#6346)