SEAD and DIRECT route does not propagate back the exception to the calling route

[ODarwish <ot...@progressoft.com>]

SEAD  and DIRECT route does not propagate back the exception to the calling
route 
If I have route1 which has exception handling block defined at route  scope
, when I call route 2 using seda or direct  point and exception generated
for any reason inside route 2,this exception does not propagated back to the
calling route  ( route 1 ) .is it by design or something wrong ?

I know that I can define the exception block at context level , but I need
to catch some exception at route level to start specific route .

my  context level exception handler have generic default route .

any advise ?





-----
Othman Darwish
ProgressSoft Corp.

--
View this message in context: http://camel.465427.n5.nabble.com/SEAD-and-DIRECT-route-does-not-propagate-back-the-exception-to-the-calling-route-tp5728748.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: SEDA and DIRECT route does not propagate back the exception to the calling route

[ODarwish <ot...@progressoft.com>]

the problem fixed by creating no error handler and refernce it in the sub
routes  ,then the exception back to the calling route 

<camel:errorHandler id="noError" type="NoErrorHandler">




-----
Othman Darwish
ProgressSoft Corp.

--
View this message in context: http://camel.465427.n5.nabble.com/SEDA-and-DIRECT-route-does-not-propagate-back-the-exception-to-the-calling-route-tp5728748p5728774.html
Sent from the Camel - Users mailing list archive at Nabble.com.