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 <jo.ra...@wiforia.com> 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: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
