> Could Spring mess up things? Or am I missing out on something here? Is my
> config wrong?
Actually your example seems a little bit complicated for me. It's hard
for me to tell what's wrong there.
Could you describe me what is the purpose of your route? Maybe I could
suggest you then how would I
Thanks, Henryk, I really appreciate your answer.
I can see that the FilterProcessor do
exchange.setProperty(Exchange.FILTER_MATCHED, matches);
and I also see that the GroupedExchangeAggregationStrategy puts the Exchange
in it's list of answer.properties.
I also set headers/properties myself (in
> And each of the aggregated messages
> will got another header set on it (HEADER1 and HEADER2 respectively).
I meant KEY1 and KEY2 :) .
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hi,
> Is there a way to make changes done to the
> header visible in further processing?
Yes. Actually modifications to the headers of the exchanged copied by
multicast are available in the aggregator.
In the example below GroupedExchangeAggregationStrategy will aggregate
two exchanges copied by
