W3C home > Mailing lists > Public > www-ws@w3.org > December 2003

Re: WSDL-1.1 fault

From: Anne Thomas Manes <anne@manes.net>
Date: Fri, 19 Dec 2003 16:09:58 -0500
Message-Id: <6.0.1.1.2.20031219155355.036abda8@localhost>
To: JRBoverhof@lbl.gov, www-ws@w3.org

Joshua,

There are quite a few errors, inaccuracies, and ambiguities in the SOAP 1.1 
and WSDL 1.1 specifications. But W3C has no jurisdiction over these 
specifications. These specs were developed copyrighted, and published by 
their respective authors (IBM, Microsoft, Lotus, Developmentor, and 
Userland). They submitted them to W3C, and W3C agreed to publish them as 
W3C Notes for discussion purposes. See the status section of the 
specifications for the status of these documents. It clearly indicates that 
a W3C Note is not a work of W3C, and it is published for information and 
discussion.

The WS-I Organization (http://www.ws-i.org) has made an effort to clarify 
the errors, inaccuracies and ambiguities in the SOAP 1.1 and WSDL 1.1 
specifications. People developing Web services using SOAP 1.1 and WSDL 1.1 
should follow the guidelines specified in the WS-I Basic Profile.

Meanwhile, W3C is developing formal standard specifications for Web 
services, including SOAP 1.2 and WSDL 2.0. SOAP 1.2  has reached the status 
of W3C Recommendation (a final standard). See 
http://www.w3.org/TR/soap12-part0/). WSDL 2.0 is still in the Working Draft 
stage. (see http://www.w3.org/TR/wsdl20/).

Regards,
Anne

At 01:20 AM 12/19/2003, Joshua Boverhof wrote:

>This is from W3C Note 15 March 2001
>
>The soap-binding schema is inconsistent with section 3.6.   The name 
>attribute isn't included in
>the type definition for faultType or its derived type bodyType.
>
><complexType name="bodyType">
>     <attribute name="encodingStyle" type="uriReference" use="optional"/>
>     <attribute name="parts" type="NMTOKENS" use="optional"/>
>     <attribute name="use" type="soap:useChoice" use="optional"/>
>     <attribute name="namespace" type="uriReference" use="optional"/>
>  </complexType>
><element name="fault" type="soap:faultType"/>
><complexType name="faultType">
><complexContent>
>  <restriction base="soap:bodyType">
>    <attribute name="parts" type="NMTOKENS" use="prohibited"/>
>  </restriction>
></complexContent>
></complexType>
>
>
>     3.6 soap:fault
>
>The soap:fault element specifies the contents of the contents of the SOAP 
>Fault Details element. It is patterned after the soap:body element (see 
>section 3.5 <http://www.w3.org/TR/wsdl#_soap:body>).
>
><definitions .... >
>   <binding .... >
>       <operation .... >
>          <fault>*
>*               <soap:fault name="nmtoken" use="literal|encoded"
>                                encodingStyle="uri-list"? namespace="uri"?>*
>          </fault>
>       </operation>
>   </binding>
></definitions>
>
>The *name* attribute relates the soap:fault to the wsdl:fault defined for 
>the operation.
>
>The fault message MUST have a single part. The *use*, *encodingStyle* and 
>*namespace* attributes are all used in the same way as with soap:body (see 
>section 3.5 <http://www.w3.org/TR/wsdl#_soap:body>), only style="document" 
>is assumed since faults do not contain parameters.
>
>
>
>
Received on Friday, 19 December 2003 16:22:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:45 GMT