Hi You can use claim check EIP or use a custom aggregation strategy with your splitter to tell Camel what data to merge as the result of the splitter.
On Thu, Jan 9, 2020 at 1:01 PM Gerald Kallas <[email protected]> wrote: > > Dear community, > > I've following snippet > > <!-- split array of consumers --> > <split streaming="true"> > <jsonpath>$.consumer[*]</jsonpath> > ... > <setProperty > name="consumerComponents"><simple>${in.body}</simple></setProperty> > </split> > <!-- log the consumer template snippet --> > <log message="template snippet: ${exchangeProperty.consumerComponents}" /> > > As I made the experience the lifetime of an exchange property is limited to > inside the split boundaries. > > Is there an other way (except a custom aggregation strategy) to define a > context wide variable? > > Best > - Gerald -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
