[
https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176895#comment-14176895
]
Susan Javurek commented on CAMEL-4494:
--------------------------------------
Hi Jens,
We'd like to pick up your fix. Would you reattach the files so we can legally
incorporate it into the product?
Thank you,
Susan
> Allow replyTo message header to be different from actual reply queue
> --------------------------------------------------------------------
>
> Key: CAMEL-4494
> URL: https://issues.apache.org/jira/browse/CAMEL-4494
> Project: Camel
> Issue Type: New Feature
> Components: camel-jms
> Affects Versions: 2.8.1
> Reporter: Jens Granseuer
> Attachments: camel-jms-replyto.diff, camel-jms-replyto2.diff
>
>
> We have an application that acts as a JMS client in the following setup:
> * a local queue manager (L) with queues for request (L.REQUEST) and reply
> (L.REPLY) messages
> * a remote queue manager (R) with queues for request (R.REQUEST) and reply
> (R.REPLY) messages
> The remote queue manager is unknown to the client application, and messages
> sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there
> is a server application listening on R.REQUEST, posting responses in R.REPLY.
> The local queue manager is unknown to the server application. Messages sent
> to R.REPLY are automatically forwarded to L.REPLY.
> The client needs to put message in L.REQUEST and receive the reply in
> L.REPLY. However, in the message header it must set R.REPLY as the reply
> queue because L.REPLY is not known to the server application.
> The Camel JMS component currently doesn't seem to support this scenario.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
