Hi,

I noticed that the error handling has changed in 3.1.0 from 3.0.1. We use a 
DeadLetterChannel and when the error has been handled, I expect the original 
route to stop and not to continue.

When we use enrich we pass the exchange property CamelErrorHandlerHandled back 
to ensure the calling route stops, but that has changed. Is this correct and 
should we change our aggregation strategy?

I added the strategy and it’s test.

Kind regards,

Remco Schoen



Reply via email to