You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2008/01/13 13:31:45 UTC
[jira] Resolved: (CAMEL-260) Splitter/aggregator scenario
[ https://issues.apache.org/activemq/browse/CAMEL-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-260.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
The Patch is applied with thanks to Roman.
> Splitter/aggregator scenario
> ----------------------------
>
> Key: CAMEL-260
> URL: https://issues.apache.org/activemq/browse/CAMEL-260
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Roman Kalukiewicz
> Assignee: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: splitter.patch
>
>
> Idea is described here: http://www.nabble.com/Re%3A-Aggregator-strategies-%28again%29-p13588242.html
> Currently splitter as a processor doesn't propagate out message at all so there is no way to use it in InOut scenario.
> Patch attached lets you to specify aggregation strategy for splitter so returning messages are aggregated into one response.
> Aggregation Strategy works the same way as in aggregator so if there is only one exchange returning then aggregation strategy is not executed at all and the result from that one exchange is used as a result of splitter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.