t; as if everything is fine.
>
> Am I using this exception handling framework in some way that it isn't
> meant to be used? Is there a bug in the RedeliveryErrorHandler? Any help
> would be appreciated.
>
> Thank You
>
>
>
--
View this message in context:
http://www.nabble.com/Camel-2.0-M3-swalllowing-exceptions--tp24834025p24854572.html
Sent from the Camel - Users mailing list archive at Nabble.com.
(new
>>> RuntimeException("Exception in message processing"));
>>>
>>> Now, when in the RedeliveryErrorHandler, this new exception policy is
>>> assigned and the failure processor is set to throw the RuntimeException.
>>> H
edeliveryErrorHandler, this new exception policy is
>> assigned and the failure processor is set to throw the RuntimeException.
>> However, the failure processor is also wrapped by the
>> RedeliveryErrorHandler
>> and when it throws the RuntimeException, the RedeliveryErrorHandler
>&g
I using this exception handling framework in some way that it isn't meant
> to be used? Is there a bug in the RedeliveryErrorHandler? Any help would
> be appreciated.
>
> Thank You
>
>
> --
> View this message in context:
> http://www.nabble.com/Camel-2.0-M3-swalllowing-exceptions--tp24834025p24834025.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
ork in some way that it isn't meant
to be used? Is there a bug in the RedeliveryErrorHandler? Any help would
be appreciated.
Thank You
--
View this message in context:
http://www.nabble.com/Camel-2.0-M3-swalllowing-exceptions--tp24834025p24834025.html
Sent from the Camel - Users mailing list archive at Nabble.com.