In my app, I need to inject some new routes. I do this by running a groovy
script as a Camel processor that adds new routes to the existing context
(exchange.context.addRoutes(new RouteBuilder(){...})). Everything works
fine except that the existing context-level onException's, that were added
before the new routes, do not catch the exceptions generated by the new
routes. But if I repeat those onException's again (at context-level) in the
groovy script along with the new routes, then they would catch the
exceptions. I would rather not duplicate the onException's.
Any insight would be greatly appreciated.
--
View this message in context:
http://camel.465427.n5.nabble.com/onException-not-getting-called-only-newly-added-onException-does-tp5796106.html
Sent from the Camel - Users mailing list archive at Nabble.com.
