Solved, it was an issue on the Throwable object, not a Camel one. Thanks.
On Tue, Nov 4, 2014 at 9:27 AM, Vadim Vararu vararu.va...@gmail.com wrote:
Yes, that works, but as i've observed, i get this way only the cause
message, and not the whole stacktrace.
On Mon, Nov 3, 2014 at 6:55 PM,
Hi
This is by design. As the on exception routes the exchange, so the
exchange needs to not have the exception in getException as that is
used to detect if a new exception is thrown during routing with
onException.
So you can grab the caused exception from the exchange property, or if
you use a
Yes, that works, but as i've observed, i get this way only the cause
message, and not the whole stacktrace.
On Mon, Nov 3, 2014 at 6:55 PM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
This is by design. As the on exception routes the exchange, so the
exchange needs to not have the exception