Its working as designed. The output from the aggregator is being executed in the route you have in between the <aggregate> and </aggregate> What comes after </aggregate> is part of the route that send the message into the aggregator, eg the input message.
If you have Camel in Action book the study chapter 8 where we cover the aggregator in much detail. On Tue, Apr 30, 2013 at 1:04 AM, RTernier <ryan_tern...@hotmail.com> wrote: > I tried doing the following: > > > The direct:foo does contain the correct XML. But when all these routes > finish and finally start processing on the main route that called all of > this, that route has the wrong XML. > > How do I get the AggregatedXML to be the actual Envelope for this process so > the Root Route has access to it? > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Aggregator-not-retaining-data-after-leaving-the-Route-tp5731759p5731760.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
