essage in context:
> http://camel.465427.n5.nabble.com/Issue-with-doTry-doCatch-not-routing-correctly-tp5720325p5720508.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redha
nabble.com/Issue-with-doTry-doCatch-not-routing-correctly-tp5720325p5720508.html
Sent from the Camel - Users mailing list archive at Nabble.com.
true is both versions. However in camel 2.8.3, the
>> "original.getException()" call returns null. In 2.10.1 it returns the
>> exception thrown in the dynamic router's destination.
>>
>>
>>
>> --
>> View this message in context:
rsions. However in camel 2.8.3, the
> "original.getException()" call returns null. In 2.10.1 it returns the
> exception thrown in the dynamic router's destination.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Issue-with-doTr
to one destination ever it doesn't
seem like I should care about this property, but the default behavior seems
flawed in this scenario when dealing with the try/catch.
Should this be filed as a bug or is this intentional?
--
View this message in context:
http://camel.465427.n5.nabble.com/I
uot; property is true is both versions. However in camel 2.8.3, the
"original.getException()" call returns null. In 2.10.1 it returns the
exception thrown in the dynamic router's destination.
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-with-doTry-doCatch
t; something wrong with the implementation above?
>
> I reverted back to version 2.8.3 and do not see this issue anymore (with any
> kind of exception), so it looks like it's new to recent releases.
>
>
>
> --
> View this message in context:
> http://camel.465427.n
th the implementation above?
I reverted back to version 2.8.3 and do not see this issue anymore (with any
kind of exception), so it looks like it's new to recent releases.
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-with-doTry-doCatch-not-routing-correctly
