You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ode.apache.org by Jonathan Coogan <Jo...@Attachmate.com> on 2009/08/03 19:02:03 UTC

Catching undeclared faults

Hi.  I recently encountered a web service that throws faults in certain
situations but the faults aren't declared in the service WSDL.  I
thought I'd still be able to catch them with a CatchAll but that doesn't
seem to work.  Is this the expected behavior?  I'm using Ode 1.3.2.
 
Thanks.
-Jon

Re: Catching undeclared faults

Posted by Jonathan Coogan <Jo...@attachmate.com>.

Thanks Alex.


On 8/3/09 10:32 AM, "Alex Boisvert" <bo...@intalio.com> wrote:

> Undeclared faults are considered failures, so you need to use the
> <faultOnFailure>true</faultOnFailure> extension.
> 
> More details at:
> http://ode.apache.org/activity-failure-and-recovery.html
> 
> alex
> 
> On Mon, Aug 3, 2009 at 10:02 AM, Jonathan Coogan <
> Jonathan.Coogan@attachmate.com> wrote:
> 
>> Hi.  I recently encountered a web service that throws faults in certain
>> situations but the faults aren't declared in the service WSDL.  I
>> thought I'd still be able to catch them with a CatchAll but that doesn't
>> seem to work.  Is this the expected behavior?  I'm using Ode 1.3.2.
>> 
>> Thanks.
>> -Jon
>>

Re: Catching undeclared faults

Posted by Alex Boisvert <bo...@intalio.com>.

Undeclared faults are considered failures, so you need to use the
<faultOnFailure>true</faultOnFailure> extension.

More details at:
http://ode.apache.org/activity-failure-and-recovery.html

alex

On Mon, Aug 3, 2009 at 10:02 AM, Jonathan Coogan <
Jonathan.Coogan@attachmate.com> wrote:

> Hi.  I recently encountered a web service that throws faults in certain
> situations but the faults aren't declared in the service WSDL.  I
> thought I'd still be able to catch them with a CatchAll but that doesn't
> seem to work.  Is this the expected behavior?  I'm using Ode 1.3.2.
>
> Thanks.
> -Jon
>