Hi See the link again, and use *only* the splitter, as it has built-in aggregation.
On Tue, May 14, 2013 at 6:36 PM, RTernier <ryan_tern...@hotmail.com> wrote: > Hey Claus, > > Thanks for the reply. I looked at that pattern, and I do get the aggregated > results back properly - in the Aggregate route. However, once processing > continues past that the exchange reverts back to what it was before it got > split->aggregated. > > Using the link you posted, I changed my batch route to the following: > > > As you can see, I aggregate after the split. Before I sent each message to > the aggregate inside the <camel:when>. > > However, this and the previous give the same result: > > When logHere3 is hit, the exchange is the same as the one that got split, > not the one that got aggregated. > > How can I fix this? > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-persist-data-from-aggregator-tp5732421p5732505.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- www.camelone.org: The open source integration conference. 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
