[
https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219329#comment-13219329
]
David J. M. Karlsen commented on CAMEL-4494:
--------------------------------------------
I definetly think it should use a DestinationResolver as the rest is spring
based - and this is the strategy interface for destination resolving.
This will allow for custom resolving:
I have an custom implementation of a DestinationResolver in order to be able to
set WMQ (WebSphere MQ) specific stuff on resolved queues.
Where can I donate that code?
It currently relies on some small parts of IBM code, but I could change that to
being reflection based.
> 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
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
