i) If an exception is thrown that is not caught by an exception handler or not 
“handled" in an exception handler then the onFailureOnly processing stops with 
an exception after the first processor - presumably because the exception is 
still present in the exchange. Can I can suppress the exception in the 
onFailureOnly handler? 

ii) You’d think that onCompleteOnly was meant to mean “the exchange went 
through the planned sequence of processors” and onFailureOnly means it did not, 
regardless of whether the exception is handled or not. Or at least it would be 
handy of that was the case allowing one to separate the concerns of dealing 
with specific exceptions as opposed to taking general premature end actions.

On 1 Sep 2014, at 11:53, Claus Ibsen-2 [via Camel] 
<ml-node+s465427n5755920...@n5.nabble.com> wrote:

> b is correct as-is, as you use an onException to handle the exception. 
> So the exchange completes successfully. 
> 
> On Sun, Aug 17, 2014 at 9:45 AM, jorabin <[hidden email]> wrote:
> 
> > Thanks for this. Hope you don't mind if I point out that my earlier post 
> > referenced in ticket 7707 misses the additional point made here under b) 
> > that routing following exception follows the onCompleteOnly path and not 
> > onFailureOnly() path - which I think it should? 
> > 
> > 
> > 
> > -- 
> > View this message in context: 
> > http://camel.465427.n5.nabble.com/Incorrect-behavior-of-onCompletion-for-exception-and-stop-tp5755272p5755320.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> 
> 
> 
> -- 
> Claus Ibsen 
> ----------------- 
> Red Hat, Inc. 
> Email: [hidden email] 
> Twitter: davsclaus 
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://camel.465427.n5.nabble.com/Incorrect-behavior-of-onCompletion-for-exception-and-stop-tp5755272p5755920.html
> To unsubscribe from Incorrect behavior of onCompletion for exception and 
> stop, click here.
> NAML





--
View this message in context: 
http://camel.465427.n5.nabble.com/Incorrect-behavior-of-onCompletion-for-exception-and-stop-tp5755272p5755975.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to