On Thu, Apr 12, 2012 at 6:17 PM, Castyn <eric.ben...@gmail.com> wrote:
> That's a nice little trick with the onWhen, I like it.
>
> Where does that fall in the scope of the exception block?
>
> Would it just run something like the following? After the onWhen runs does
> the flow pass through the to the statements afterwards, or is there some
> sort of "else" clause I need to use to control flow more?
>
No its part of the <exception>, so its just an *extra* check, that it
must be that kind of exception, and the onWhen predicate must *also*
be true.
So it should be after <exception>
> <onException>
> <exception>org.apache.cxf.interceptor.Fault</exception>
> <redeliveryPolicy maximumRedeliveries="0" />
> <handled><constant>true</constant></handled>
> <onWhen>
> <simple>${exception.getClass().getSimpleName()} ==
> 'WstxEOFException'</simple>
> <log message="Woodstock XML Exception"/>
> </onWhen>
> <log message="CXF Fault" loggingLevel="ERROR"/>
> </onException>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Trapping-Errors-Help-tp5633932p5636126.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
