Hi Yes its this eip http://camel.apache.org/composed-message-processor.html
The Camel splitter has a built-in aggregation stragegy which is much easier to use than split + aggregate. See the example on the page above, about using ONLY splitter. On Wed, Feb 27, 2013 at 1:28 PM, developpef <src...@orange.fr> wrote: > Well, after my SPLIT I use an aggregation Strategy with completionPredicate > to Exchange.SPLIT_COMPLETE. > > So if I understand, I would rather write : > > .split(body(), myAggregationStrategy) > (... split operations ...) > .end() > > rather than : > > .split(body()) > (... split operations ...) > .aggregate(...) > .completionPredicate(header(Exchange.SPLIT_COMPLETE).isEqualTo(Boolean.TRUE)) > > Am I right? And in the first case, will my aggregation strategy complete on > Exchange.SPLIT_COMPLETE as well? > > > > ----- > http://developpef.blogspot.com > -- > View this message in context: > http://camel.465427.n5.nabble.com/Split-an-empty-list-tp5728214p5728221.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
