activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6274) Add option to composite destinations to set originalMessage header
Date Mon, 02 May 2016 19:37:12 GMT

    [ 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)

Mime
View raw message