You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/05/05 16:13:12 UTC
[jira] [Resolved] (AMQ-6274) Add option to composite destinations
to set originalMessage header
[ https://issues.apache.org/jira/browse/AMQ-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-6274.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.13.4
5.14.0
> 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
> Fix For: 5.14.0, 5.13.4
>
>
> 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)