camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Granseuer (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
Date Tue, 20 Mar 2012 08:49:39 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jens Granseuer updated CAMEL-4494:
----------------------------------

    Attachment: camel-jms-replyto2.diff

Hm, I thought I had done so. There doesn't seem to be a way to change it without reuploading,
though, correct?
                
> 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, 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 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

        

Mime
View raw message