You can use an aggregation strategy on the splitter to merge any changes you want on the exchange that is routed after all the splitting is done.
By default the exchange being routed is a copy of the input exchange (untouched). On Fri, Nov 1, 2013 at 7:36 PM, javamonkey79 <[email protected]> wrote: > With following: > > <split> > <tokenize token="\r\n" /> > <setOutHeader > headerName="caseCount"><constant>42</constant></setOutHeader> > <setHeader > headerName="caseCount"><constant>42</constant></setHeader> > <setProperty > propertyName="caseCount"><constant>42</constant></setProperty> > </split> > <to uri="log:foo?showAll=true&multiline=true" /> > > When I run this, the caseCount header\property does not show up in the log. > It seems the splitter is not letting headers\properties to be set on the > pipeline. Is there any way to do this? (I've only set the value 42 for > demonstration, in reality, I'd like to grab something via simple, like the > split count). > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/preserve-headers-properties-in-split-tp5742525.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
