Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D00BA17D34 for ; Tue, 21 Oct 2014 09:40:34 +0000 (UTC) Received: (qmail 38300 invoked by uid 500); 21 Oct 2014 09:40:34 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 38268 invoked by uid 500); 21 Oct 2014 09:40:34 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 38259 invoked by uid 99); 21 Oct 2014 09:40:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Oct 2014 09:40:34 +0000 Date: Tue, 21 Oct 2014 09:40:34 +0000 (UTC) From: "Willem Jiang (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-4494: ----------------------------------- Assignee: Willem Jiang > 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 > Assignee: Willem Jiang > 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 was sent by Atlassian JIRA (v6.3.4#6332)