[
https://issues.apache.org/jira/browse/CAMEL-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486948#comment-13486948
]
Claus Ibsen commented on CAMEL-5579:
------------------------------------
I have improved the code a bit which allows to transfer the completion from the
exchange property to the message body. This makes it even easier to do
aggregation strategies where you want to build together a List<V>. This is IMHO
better than the exchange property where the grouped exchanges is stored by
default in the old logic.
> Add an abstract grouped by aggregator strategy that users can extend from.
> --------------------------------------------------------------------------
>
> Key: CAMEL-5579
> URL: https://issues.apache.org/jira/browse/CAMEL-5579
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claudio Corsi
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: camel-core,
> Fix For: 2.11.0
>
> Attachments: AbstractGroupedByValueAggregationStrategy.java,
> grouped-aggregate-strategy.tar.gz, GroupedByExchangeAggregationStrategy.java
>
>
> The current GroupedExchangeAggregationStrategy will combine a list of
> exchange instances for a given correlation expression and propagate the
> exchange with that list. This is great as long as users are content with
> processing the list of exchanges.
> What about users that would like to extract data from the exchange and add
> that to the forwarded list? This is something that require users to create
> their own strategy.
> What I propose is that we provide base class for users to extend such that it
> manages the grouped list and have the user state and return the type of
> instances that will be added to the grouped list.
> I will attach a base class that users can extend and an example of a
> sub-classed version that will return a list of exchange instances like the
> default GroupedExchangeAggregateStrategy camel core class.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira