Uhh probably not. Proprietary code you know. I would look for another problem. I know the exception handlers are working fine so if you say you are getting an exception without even the processor in the route, its time to turn the tracer to max and pretend you are the computer. Something weird is going on there.
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Hardcore Java (2003) and Maintainable Java (2012)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 <http://www.linkedin.com/pub/robert-simmons/40/852/a39>* On Mon, Dec 23, 2013 at 4:51 AM, jguerra <jg.gue...@gmail.com> wrote: > Good news.... Please could you provide more information about the scenarios > you test?. Did you handle java.sql.SQLException?. What kind of environment > did you test it.?. Could you please attach the whole dependency tree > running > in your tests for your handlers (Database, Spring, etc...)? > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Problem-with-exception-handler-onException-on-Camel-2-12-X-routes-tp5742605p5745185.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
