Hi See this EIP http://camel.apache.org/composed-message-processor.html
And use the splitter with the aggregation repository. Then you can aggregate them easily back again in the same route. On Mon, May 13, 2013 at 7:10 PM, RTernier <ryan_tern...@hotmail.com> wrote: > I'm having an issue with aggregator. > > I have an incoming Web Service request that will be split into 2 messages > and have the responses of both web requests aggregated together. This works > fine, and I do get a good aggregated message within the aggregation route. > > However, once I'm out of that route and it goes back to the main calling > route (bottom one) the message is not what is aggregated, it's one of the > responses from a web service call. How do I force the aggregated message to > be the envelop that camel uses? > > Here is my spring XML: > > > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-persist-data-from-aggregator-tp5732421.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
