[
https://issues.apache.org/jira/browse/ARTEMIS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880942#comment-15880942
]
ASF subversion and git services commented on ARTEMIS-970:
---------------------------------------------------------
Commit 01465035c0dc58c5b5c64b7573462bcf6804a048 in activemq-artemis's branch
refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=0146503 ]
ARTEMIS-970 handle indeterminate JMS destination
> Artemis Cross Protocol to JMS does not work
> -------------------------------------------
>
> Key: ARTEMIS-970
> URL: https://issues.apache.org/jira/browse/ARTEMIS-970
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martyn Taylor
> Assignee: Justin Bertram
> Fix For: 2.0.0
>
> Attachments: 0001-Test-for-Cross-Protocol.patch
>
>
> After the latest changes around the addressing scheme, the Artemis JMS Core
> client no longer uses prefixes e.g. "jms.queue." to determine the destination
> type of a message.
> Instead it relies on a message header sent from the:
> SimpleString HDR_ROUTING_TYPE = new SimpleString("_AMQ_ROUTING_TYPE");
> This currently isn't getting set when doing cross protocol.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
