-
1. Re: exposing Exception set in Camel DefaultExchange ?
kcbabo Oct 25, 2012 7:12 AM (in response to jbride)This shouldn't happen. The routes we define internally include an exception handler specific to HandlerException (heh, that sounds weird). If a HandlerException is thrown in a route, the exception should be "caught" in the route and channeled into a SY fault. Do you have a basic app we can use to reproduce this?
-
2. Re: exposing Exception set in Camel DefaultExchange ?
jbride Oct 25, 2012 8:13 AM (in response to kcbabo)yes. i'm able to reproduce this using the transform-jaxb quickstart with one modification to transform-jaxb/src/main/resources/META-INF/switchyard.xml :
14 from="java:org.switchyard.quickstarts.transform.jaxb.OrderAck" 15 to="{rn:switchyard-quickstart:transform-jaxb:1.0}orderAck" 16 contextPath="org.switchyard.quickstarts.transform.jaxb"/>
notice the removal of the beginning 'u' in the namespace of the "to" path.
hope this helps. jeff
-
3. Re: exposing Exception set in Camel DefaultExchange ?
kcbabo Oct 25, 2012 9:13 AM (in response to jbride)Ah, so that adds a bit more context. This is happening on the return path and there may be a hole in our exception handling with the return route. More to follow ...
-
4. Re: exposing Exception set in Camel DefaultExchange ?
splatch Oct 30, 2012 5:16 AM (in response to kcbabo)This issue was really missed in 0.6. Camel Exchange Bus was able to handle HandlerException and in general did not expect any other exceptions. When RuntimeException was thrown from handler then it was breaking the chain with to handle. Linked issue contains pull request which catches all exceptions, ie. if RuntimeException is thrown then whole exchange is marked as fault.