RE: Clarification needed: Part 3 sec 2.8.1 and 2.8.2: soap fault codes

Thank you for your comment - we tracked this as a Last Call comment LC94
[1].  The Working Group closed this issue without action, after the
conversation at [2] (which you participated in).

If we don't hear otherwise within two weeks, we will assume this
satisfies your concern.

[1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC94
[2]
http://lists.w3.org/Archives/Public/www-ws-desc/2005Feb/att-0013/2005020
3-ws-desc-minutes.html#item12 

> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of David Booth
> Sent: Sunday, December 12, 2004 1:00 PM
> To: public-ws-desc-comments@w3.org
> Subject: Clarification needed: Part 3 sec 2.8.1 and 2.8.2: soap fault
> codes
> 
> 
> Regarding part 3 sec 2.8.1 and 2.8.2: soap fault codes, the meaning of
> the {soap fault code} seems unclear.
> 
> Does the fault message type determine the soap fault code, or vice
> versa?  For example, given the following:
> 
> <binding . . . >
>   <fault ref="tns:myFaultMessage"
> 	wsoap:code="foo" />
> </binding
> 
> which of the following interpretations applies?
> 
> a. If the actual error condition causing the fault corresponds to SOAP
> code foo, then transmit a fault of type tns:myFaultMessage.
> 
> b. If the actual error condition causing the fault corresponds to
> tns:myFaultMessage, then transmit SOAP code foo.
> 
> If (a) is the correct interpretation, then what happens if an error
> corresponding to a different SOAP code occurs?  Does this imply that a
> tns:myFaultMessage will NOT be sent if the SOAP code is NOT foo?
> 
> --
> 
> David Booth
> W3C Fellow / Hewlett-Packard
>

Received on Saturday, 28 May 2005 22:19:53 UTC