axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <stev...@iseran.com>
Subject Re: MustUnderstand faults
Date Fri, 08 Aug 2003 01:24:07 GMT
Simon Fell wrote:

> On Thu, 07 Aug 2003 15:43:13 -0700, in soap you wrote:
> 
> 
>>When getting a DIME service to work w/ WSE1.0, I discovered that WSE was 
>>send a MustUnderstand header with WS-routing info. Axis, not 
>>understanding such headers, threw an exception.
>>
>>Unfortunately, the exception got thrown after the pivot point was 
>>reached -as far as my service cared, all was well, yet the fault was 
>>still being thrown.
>>
>>1. What is the rules about when mustunderstand headers are processed? Is 
>>that they must be understood or faulted, but there is no rule as to 
>>whether the action can be dispatched first.
>>
>>2. how about we add some xml element to an AxisFault/SOAPFault that 
>>indicates that an exception was thrown *After* the pivot point. CORBA 
>>does this with its exceptions, and it may be useful for clients.
>>
>>If I'm going to write (2), what is the best way for me to go about doing 
>> it.
>>
>>-steve
> 
> 
> The SOAP spec calls for the message to be only processed if it fully
> understands all the mandatory parts. Sounds to me that your service
> should never get called in this case.

which means of course, that all MU handlers must be on the inbound path 
of the message, before it gets to the pivot point. Hmmm.

I still like the idea of an element in a soapfault that says whether 
something got to the method or not, as it can be used in other faults.


Mime
View raw message