Hello,
maybe the onWhen(<predicate>) construct can help out here. The idea is to
use the "CamelMessageHistory" to check for the last processor in the Camel
route that was accessed, which is the failing one. The onWhen(...) construct
is then used to catch the filtered exceptions.
This could look similar to that:
onException(Exception.class).onWhen(new
ExceptionGuard("process3")).handled(true).end();
So far the idea, the practical use needs to be evaluated. A sound concept in
Camel would be preferred.
Best regards,
Daniel Ritter
--
View this message in context:
http://camel.465427.n5.nabble.com/Try-Catch-like-onException-with-Blueprint-DSL-tp5751973p5752007.html
Sent from the Camel - Users mailing list archive at Nabble.com.
