[
https://issues.apache.org/jira/browse/CAMEL-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019218#comment-13019218
]
Claus Ibsen commented on CAMEL-3855:
------------------------------------
No thats frankly not intuitive, to aggregate using a constant expression, and
all into a list. If you read the EIP book then thats not the point they explain
about the pattern. There are many other uses cases where you must aggregate by
a correlation key part of the message and so forth.
The current solution to ensure the end user specify the
- correlation expression
- aggregation strategy
- completion conditions
Works the best as there are no surprises with defaults and what not. The end
user configure the EIP according to their needs.
> make aggregate() easier to use for the common case
> --------------------------------------------------
>
> Key: CAMEL-3855
> URL: https://issues.apache.org/jira/browse/CAMEL-3855
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Ben O'Day
> Assignee: Ben O'Day
> Priority: Minor
> Attachments: CAMEL-3855.patch
>
>
> Currently, an expression and strategy are required to use aggregate().
> Perhaps, we could set a default expression (constant(true), etc) and strategy
> (either groupExchanges() or the attached AggregateAsListStrategy, etc).
> For example, either of these could make a good intuitive default (still
> requiring a completionSize/Interval, etc)
> aggregate() == aggregate(constant(true)).groupExchanges()
> or
> aggregate() == aggregate(constant(true), new AggregateAsListStrategy())
> See this discussion for more
> information....http://camel.465427.n5.nabble.com/Default-Behavior-for-aggregate-td4296790.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
