The CamelSplitComplete is at each exchange level that gets split. In case the below block is aggregating only a specific set of filtered data, then the exchanges that are getting into this block may not be the last exchange from the bigger set of exchanges and hence the block posted will never get executed. This header works pretty fine without any filtering applied.
However, Is there a better way of identifying the end of records (file) processing with filtering of the records? -Ganga -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Aggregator-Completion-based-on-CamelSplitComplete-tp5774653p5774659.html Sent from the Camel - Users mailing list archive at Nabble.com.
