camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From harald <>
Subject Re: On Route Completion when using the aggregator
Date Fri, 06 Mar 2015 19:03:42 GMT
You are right, it’s in the properties not the header - sorry for that one.

If the implementation of the AggregationStrategy keeps the properties from the first exchange
to be aggregated with the next 999 ones, the aggregated message will not contain the CamelSplitComplete
because it is part of the last.

Easiest solution I see is to send a message at the end of route 1 to the seda queue indicating
the end. Depends on what the second route has to do with it.

If this does not fit your needs, any details about the routes?

View raw message