Hello Claus,
Thank you for your response.
Yes, I understood that the observed behaviour is by-design in Camel.
Yet, as this does not fulfill our particular requirement, I wanted to know
how to use Camel to behave differently.
More specifically : we do need the firstRoute to continue the processi
Hi
What Camel does is correct there was an exception and it was handled, and
you could build a custom response in the onException block as you did. And
then the routing stops and returns to the caller.
The first route does not see the exception, so either you turn off error
handling in the second
Hello Raymond,
The default Error Handler
(org.apache.camel.processor.errorhandler.DefaultErrorHandler) is already
fine to make the redeliveries and calling the exception policy without
explicitly specifying it
( and I don't need the Deadletter capable error handler
(org.apache.camel.processor.erro
Did you try to use an errorHandler? Some like this:
from("seda:a")
// here we configure the error handler
.errorHandler(deadLetterChannel("seda:error"))
// and we continue with the routing here
.to("seda:b");
Then you can set the errorHandler direct
