I am not sure if this pattern matches. In my case i have to aggregate a data base result set (aggregating same primary key due to a 1:n relation). After this aggregation a need parallelProcessing.
The route worked fine without the aggregator and parallelProcessing and it works fine with aggregator and without parallelProcessing. For me it seems that aggreagator+parallelProcessing some how breaks the onCompletion/isDone semantik. In my case onCompletion is called before any of the processors are run. -- View this message in context: http://camel.465427.n5.nabble.com/When-original-exchange-isDone-with-aggregator-tp5772577p5772599.html Sent from the Camel - Users mailing list archive at Nabble.com.
