[Camel-users] Global exception policy across Route builder configure methods

Hi,
If I understand correctly, the onException() defined in the configure method
of a Routebuilder is global across all routes subsequently defined in that
method using the Camel DSL.
Is there a way to make these onException() global across routebuilder such
that I can define in one place something like,
onException(myexception.class).to(mybean)
onException(myexception2.class).to(mybean2)
just once for apply it to all possible routes (some of which may be added
later) in the given camel context irrespective of the route builder used to
create them?

Thanks in advance,
-v-



--
View this message in context: http://camel.465427.n5.nabble.com/Global-exception-policy-across-Route-builder-configure-methods-tp5719075.html
Sent from the Camel - Users mailing list archive at Nabble.com.

On 11 September 2012 16:26, vishal1981 wrote:
Alright thanks.
But then global scope doesn't really means global to the camelcontext. Its
global to the routes currently being defined.
Thanks for your help



--
View this message in context: http://camel.465427.n5.nabble.com/Global-exception-policy-across-Route-builder-configure-methods-tp5719075p5719131.html
Sent from the Camel - Users mailing list archive at Nabble.com.

On Tue, Sep 11, 2012 at 6:14 PM, Andreas Jacobsen wrote:

My understanding is that exception policies defined in global scope
are actually global. You could set up a seperate routebuilder
specifically for the global exception policies.

Claus's suggestion works too, since the same exception policies will
be created several times.

On 11 September 2012 22:17, Mitko Kolev wrote:
Hi,

the "global" scope mentioned here
http://camel.apache.org/exception-clause.html in this case actually means
"route builder" scope.
For example the rule for ValidationException will trigger for both routes
in the same route builder (at least with the Camel version 2.6.x with which
I did the test to find this out some months ago)

configure(){
...
onException(ValidationException.class).
to("activemq:validationFailed");

from("seda:inputA").
to("validation:foo/bar.xsd", "activemq:someQueue");

from("seda:inputB").to("direct:foo").
to("rnc:mySchema.rnc", "activemq:anotherQueue");
}

However, if you split this in 2 route builders like this

configure(){
...
onException(ValidationException.class).
to("activemq:validationFailed");

from("seda:inputB").to("direct:foo").
to("rnc:mySchema.rnc", "activemq:anotherQueue");
}

&

configure(){
...
from("seda:inputB").to("direct:foo").
to("rnc:mySchema.rnc", "activemq:anotherQueue");
}

the onException will not process ValidationExceptions from the second route
("seda:inputB"). In this sense the onException clause is not context
scoped, but rather route builder scoped.

I guess the confusion comes from the Sping DSL format, as the onException
clause is within the camelContext tag, so you might think the onException
definition is "camel context" scoped (configuration of the camel context).


Regards,
Mitko

On Tue, Sep 11, 2012 at 6:14 PM, Andreas Jacobsen <
andreas@andreasjacobsen.com> wrote:

I finally got some time to help with this, and have fixed the issue reported.

I also updated the error handler docs to better reflect the scopes for
Java DSL vs XML DSLs.
http://camel.apache.org/error-handling-in-camel.html