Hi Yogesh is right when he suggest to use the aggregation strategy of the multicast. This allows you full control of the assembly of the outgoing message when all the parallel multicasted messages is complete.
By default the multicast will just keep the last message as the outgoing message. (eg the UseLatestAggregationStrategy) On Tue, May 8, 2012 at 5:10 AM, ychawla <premiergenerat...@yahoo.com> wrote: > Hi Tyler, > Are some of the headers in there but not all of them? If you want, you can > use an aggregator with the multicast and set a custom aggregation strategy: > > http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html > > This way you can process each exchange in the multicast, grab your headers, > and see them on the new exchange. See the multicast page for more details > on a custom aggregator: > > http://camel.apache.org/multicast.html > > Thanks, > Yogesh > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/multicast-and-setting-header-tp5691098p5692642.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
