You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/12 07:52:20 UTC
[jira] [Commented] (CXF-7008) Regression: CXF-5788 - JMS
replyToDestination doesn't work
[ https://issues.apache.org/jira/browse/CXF-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418486#comment-15418486 ]
ASF GitHub Bot commented on CXF-7008:
-------------------------------------
GitHub user tadayosi opened a pull request:
https://github.com/apache/cxf/pull/156
[CXF-7008] Regression: CXF-5788 - JMS replyToDestination doesn't work
See https://issues.apache.org/jira/browse/CXF-7008
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tadayosi/cxf CXF-7008
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/156.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #156
----
commit 0f51e22bc7e13630aeac1996fba4d06e97dea37c
Author: Tadayoshi Sato <sa...@gmail.com>
Date: 2016-08-12T07:06:48Z
[CXF-7008] Regression: CXF-5788 - JMS replyToDestination doesn't work
----
> 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
>
> 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)