activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1207) [Core JMS Client] Align order of when setClientId can be called with AcitveMQ5 and QPID
Date Wed, 07 Jun 2017 14:19:18 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040951#comment-16040951
] 

ASF subversion and git services commented on ARTEMIS-1207:
----------------------------------------------------------

Commit e8fa02bf80118738c52489c4bf2511aa0d1ef5b8 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=e8fa02b ]

ARTEMIS-1207: Align when setClientId can be called

Update ActiveMQConnection to change/alighn behaviour for addtional methods:
- getMetaData
- stop

Adding test to avoid regression.

This is aligning with qpid-jms and openwire clients


> [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)

Mime
View raw message