Hello,
maybe the onWhen() 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
Thank you. It seemed to me that this was not the intended use. However, is
there any chance to ensure the described/required behavior with Camel ("Do
you know a way how to ensure the same behavior?")?
The doTry/doCatch seems to be one way to achieve this. Unfortunately, it
comes with several "unwa
Hello,
I am analyzing the Exception handling capabilities of Apache Camel and might
have run into an inconsistency between the Java DSL and Blueprint, when
using onException on a route-processor level.
Due to several reasons, I do not want to use the doTry/doCatch handling, but
the onException co
