Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1378996158796-5739261.post@n5.nabble.com>
References: <1378996158796-5739261.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 12 Sep 2013 16:40:07 +0200
Message-ID: 
 <CAGB5yN=4GMXUo+258_bAkBz-ZwuY05XfKi1f0zSOoE6t_QYS3w@mail.gmail.com>
Subject: Re: DefaultErrorHandler and "nested" routes
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Move it outside the route so its context scoped onException instead.


On Thu, Sep 12, 2013 at 4:29 PM, fbarbat <fbarbat@gmail.com> wrote:
> Hi,
>
> I have these routes:
>
> from("direct:a").routeId("1")
> .onException(Exception.class).handled(true).to("direct:d").end()
> .to("direct:b").to("direct:c");
>
> from("direct:b").routeId("2").process(new ThrowingExceptionProcessor());
> from("direct:c").routeId("3").process(new OkProcessor());
>
> from("direct:d").routeId("4").process(new ExceptionProcessor());
>
> Let's suppose a message comes to route 1. If ThrowingExceptionProcessor
> throws an exception I would expect that the exception would be handled by
> the onException clause. However, it looks like the exception is propagated
> directly to the consumer ("direct:a"). How can I force the exceptions thrown
> inside "child routes" to be managed by the onException clause?
>
> Thanks.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/DefaultErrorHandler-and-nested-routes-tp5739261.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen