[
https://issues.apache.org/jira/browse/CXF-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418555#comment-15418555
]
ASF GitHub Bot commented on CXF-7008:
-------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/cxf/pull/156
> Regression: CXF-5788 - JMS replyToDestination doesn't work
> ----------------------------------------------------------
>
> Key: CXF-7008
> URL: https://issues.apache.org/jira/browse/CXF-7008
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.1.7
> Reporter: Tadayoshi Sato
> Assignee: Freeman Fang
>
> Fix for CXF-5788 is not applied to CXF 3.x branches. According to the source
> code of
> [JMSConfiguration|https://github.com/apache/cxf/blob/cxf-3.1.7/rt/transports/jms/src/main/java/org/apache/cxf/transport/jms/JMSConfiguration.java]:
> {code:java}
> /**
> * Destination name to listen on for reply messages
> */
> private String replyDestination;
> [...]
> /**
> * Destination name to send out as replyTo address in the message
> */
> private String replyToDestination;
> {code}
> so in client side if we set {{replyDestination}} to {{queue1}} but
> {{replyToDestination}} to {{queue2}} on {{JMSConfiguration}}, we expect that
> the request message has header {{JMSReplyTo="queue2"}} but the client listens
> on {{queue1}} for a reply. It works as expected on CXF 2.7.18, but starts not
> to work since 3.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
