ng 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-except
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-except
ge 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.
complete.expectedBodiesReceived("finish", "stop", "except");
> MockEndpoint failed = getMockEndpoint("mock:failed");
> failed.expectedBodiesReceived("faulted");
> template().sendBody("direct:input","finish"
uot;faulted");
template().sendBody("direct:input","finish");
template().sendBody("direct:input","stop");
template().sendBody("direct:input","fault");
template().sendBody("direct:input","except");Thread.sleep(1000);
assertMockEndpointsSatisfied();}
--
View this message in context:
http://camel.465427.n5.nabble.com/Incorrect-behavior-of-onCompletion-for-exception-and-stop-tp5755272.html
Sent from the Camel - Users mailing list archive at Nabble.com.
