W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

New Issue: Fault Code Restrictions

From: Marc Hadley <marc.hadley@sun.com>
Date: Tue, 12 Feb 2002 13:08:18 +0000
Message-ID: <3C6913C2.1040203@sun.com>
To: XML Protocol Discussion <xml-dist-app@w3.org>
Part 1, Section 2.6 contains the following paragraph:

"If processing is unsuccessful, exactly one fault MUST be generated by 
the node. Header-related faults other than mustUnderstand faults (see 
4.4 SOAP Fault) MUST be SOAP Sender or DataEncodingUnknown faults (see 
4.4.5 SOAP Fault Codes) and MUST conform to the specification for the 
corresponding SOAP header block. Faults relating to the body MUST be 
SOAP Sender or DataEncodingUnknown faults (see 4.4.5 SOAP Fault Codes)."

The restrictions on the type of faults that may be generated seems 
strange. E.g. why couldn't header processing lead to a Receiver fault 
(out of memory etc...).

This restriction was not present in the 2nd Oct 2001 WD[1] and first 
appeared in the 17th Dec 2001 WD[2]. It's source seems to be the rewrite 
proposed to address distinctions between header and body[3]. I have been 
unable to find any issue resolution pertaining to these new restrictions.

I suggest that we open a new issue on this and would like to propose the 
following rewrite as a resolution:

"If processing is unsuccessful, exactly one fault MUST be generated by 
the node. Header-related faults other than mustUnderstand faults MUST 
conform to the specification for the corresponding SOAP header block."

Regards,
Marc.

[1] http://www.w3.org/TR/2001/WD-soap12-part1-20011002/
[2] http://www.w3.org/TR/2001/WD-soap12-part1-20011217/
[3] http://lists.w3.org/Archives/Public/xml-dist-app/2001Dec/0027.html

-- 
Marc Hadley <marc.hadley@sun.com>
XML Technology Centre, Sun Microsystems.
Received on Tuesday, 12 February 2002 08:08:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT