Try turn off error handling in the sub routes, eg use .noErrorHandler()
On Tue, Sep 2, 2014 at 8:20 PM, sandp <sandeepred...@gmail.com> wrote:
>
> Hi, I'm trying to understand how the scenario can be implemented :
> *direct:parent* calls a RESTFul service, that succeeds, the exchange is
> multicast to other endpoints with *direct:child1* and *direct:child2*.
>
> Now, *direct:child1* results in *IOException*, so, on redelivery, route*
> direct:child1* is retried. But I'm looking at the possibility of doing a
> retry from direct:parent ( actually, IOException in route direct:child1 was
> a result of corrupt file returned by the restlet endpoint in direct:parent.
> )
>
> *from("direct:parent")*
> .to("restlet"some_URL")
> .streamCaching()
> .multicast().to("direct:child1","direct:child2")
> .end();
>
>
> *from("direct:child1")*
> .to("file:somePath")
> .end();
>
>
> *from("direct:child2")*
> .unmarshal(bindy)
> .to("direct:childOf2")
> .end();
>
>
> Link to Camel FAQ for retry
> <http://camel.apache.org/how-do-i-retry-processing-a-message-from-a-certain-point-back-or-an-entire-route.html>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-2-13-1-Retry-starting-from-Parent-Route-on-a-sub-route-failure-tp5755977.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/
