[
https://issues.apache.org/jira/browse/ARTEMIS-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024822#comment-16024822
]
ASF subversion and git services commented on ARTEMIS-1178:
----------------------------------------------------------
Commit b1ad8f3adf51fa96069e1eccd7b87e9dff85223d in activemq-artemis's branch
refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=b1ad8f3 ]
ARTEMIS-1178 backwards compatibility issues
This commit has 2 changes for backwards compatibility with older
clients:
1) A "bindings query" will now detect if the client is both JMS and
"old" (i.e. pre-2.0) and will prefix the returned queue names with the
old prefix (i.e. "jms.queue."). This will allow the old client to
properly detect whether or not a queue exists in its auto-creation
logic.
2) When messages are dispatched to a consumer there is logic to detect
if the consumer is both JMS and "old" and will prefix the "address"
on the message with "jms.queue." or "jms.topic." as appropriate
(if it's not already prefixed).
> Backwards compatibility issues
> ------------------------------
>
> Key: ARTEMIS-1178
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1178
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Fix For: 2.2.0
>
>
> As noted in a recent mailing list thread, there is an issue with older (e.g.
> 1.4.x) clients and the new broke (i.e. 2.x). The thread notes a problem with
> getJMSDestination() but there's one other as well related to the
> behind-the-scenes bindings query which the client does to determine whether
> or not to auto-create the destination.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
