Could you post some code to illustrate your case, so we can provide more accurate feedback? The way that onException handlers are set up depends on whether you use Java DSL or Spring DSL.
Regards, Raúl. On Mar 5, 2013, at 13:43, ddewaele wrote: > Hi, > > I have a Camel Spring XML where I define a camelcontext containing 2 routes. > The main route is embedded inside the camlContext. > At some point in the main route, based on someCondition, I need to decide to > do either > > * standard processing (here I just need trigger a single camel processor) > * complex processing (here I would like to jump into a new route). > > The reason why the complex-route was introduced was simply to encapsulate > the steps required to do the complex processing. > > Question : Is this the correct way of doing it (defining a new route and > jumping into that route from an existing route) ? > > > > This seems to work fine except for one thing : > > Both the main-route and the complex-route have an onException element. > When an exception occurs and even when complexProcessingRequired=false and > the complex-route is never triggered, sometimes the onException block of the > complex-route is triggered instead of the onException block of the > main-route. > > Question : any ideas why it would trigger an onException block of the > complex-route during standard processing (complexProcessingRequired=false) > > Thanks in advance > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-multiple-nested-routes-in-one-context-tp5728576.html > Sent from the Camel - Users mailing list archive at Nabble.com.
