Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 2 May 2016 19:37:12 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12963916.1461951502000.89233.1462217832813@Atlassian.JIRA>
In-Reply-To: <JIRA.12963916.1461951502000@Atlassian.JIRA>
References: <JIRA.12963916.1461951502000@Atlassian.JIRA> <JIRA.12963916.1461951502101@arcas>
Subject: [jira] [Commented] (AMQ-6274) Add option to composite destinations
 to set originalMessage header
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 02 May 2016 19:37:15 -0000


    [ https://issues.apache.org/jira/browse/AMQ-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267343#comment-15267343 ] 

Timothy Bish commented on AMQ-6274:
-----------------------------------

Unit tests to demonstrate the issue and the use case you are shooting for are a good place to start. 

> Add option to composite destinations to set originalMessage header
> ------------------------------------------------------------------
>
>                 Key: AMQ-6274
>                 URL: https://issues.apache.org/jira/browse/AMQ-6274
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.13.2
>            Reporter: Quinn Stevenson
>            Priority: Minor
>
> Composite Destinations are a great way to wiretap messages, but the resulting messages don't have any information in them about where they originally came from.
> I'm proposing to add an option to composite destinations ( addHeaders ) that will enable the addition of the originalDestination header to the messages.  The option will be disabled by default to preserve existing behavior by default.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)