#1-3 are correct, for #4, with the fault removed (or converted to an
exception), the exception pipeline will not be short-circuited...
that being said, I'm not sure why the HandleFault interceptor isn't being
called or converting this..I'll look into it
On Thu, May 12, 2011 at 8:49 AM, Jens [via Camel] <
ml-node+4390611-1845085697-45...@n5.nabble.com> wrote:
> >> Doesn't from("....").handleFault() work either?
> >
> > Building on my previous example I'm assuming it should look like this?
> > ...
> > If so then no, that doesn't work, either.
>
> I think I should clarify. I'm not quite sure but I believe that what's
> happening might be this:
>
> 1. The CXF endpoint gets called and causes a fault.
> 2. The HandleFault interceptor (assuming it gets called; haven't been able
> to verify that yet) turns the fault into an exception
> 3. The first processor in the onException route gets called; after this
> 4. The route is still short-circuited because getException is non-null
>
> Does that sound plausible?
>
> What does work is inserting a processor first thing in the onException
> route that removes the fault and instead of calling setException puts the
> fault into the exchange under the EXCEPTION_CAUGHT property. It would be
> nice if that effect was possible with "handled" without lots of manual
> intervention.
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4390611.html
> To unsubscribe from Does onException not support multiple statements?, click
> here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4381958&code=YmVuLm9kYXlAaW5pdGVrY29uc3VsdGluZy5jb218NDM4MTk1OHwxNDU1ODI4NTg5>.
>
>
-----
Ben O'Day
IT Consultant -http://benoday.blogspot.com
--
View this message in context:
http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4390637.html
Sent from the Camel - Users mailing list archive at Nabble.com.
