You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Aaron Whiteside (JIRA)" <ji...@apache.org> on 2014/12/11 03:33:12 UTC
[jira] [Created] (CAMEL-8143) MulticastProcessorDefinition should
allow one to specify the default aggregation strategy of
AggregationStrategies.useOriginal().
Aaron Whiteside created CAMEL-8143:
--------------------------------------
Summary: MulticastProcessorDefinition should allow one to specify the default aggregation strategy of AggregationStrategies.useOriginal().
Key: CAMEL-8143
URL: https://issues.apache.org/jira/browse/CAMEL-8143
Project: Camel
Issue Type: Improvement
Components: camel-core, documentation
Affects Versions: 2.14.0
Reporter: Aaron Whiteside
Priority: Minor
MulticastProcessorDefinition should allow one to specify the default aggregation strategy (or behavior) of AggregationStrategies.useOriginal() without having to create a bean instance of it and reference it using strategyRef="".
The wiki page could also be updated to clarify that it does indeed modify the original exchange (request message), in the way of returning the result of the last processor inside the multicast block.. as opposed to passing a copy of the original to each processor in the multicast block.
>From the WIKI page:
{quote}
The Multicast allows to route the same message to a number of endpoints and process them in a different way. The main difference between the Multicast and Splitter is that Splitter will split the message into several pieces but the Multicast will not modify the request message.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)