W3C home > Mailing lists > Public > public-ws-chor@w3.org > May 2005

Fault name in WSDL1.1

From: Gary Brown <gary@pi4tech.com>
Date: Wed, 18 May 2005 16:13:19 +0100
Message-ID: <00f301c55bbc$215699b0$0200a8c0@GPB1>
To: "'WS-Choreography List'" <public-ws-chor@w3.org>
Responding to Nick's comment on yesterday's conference call, regarding the fault name attribute in WSDL1.1 not being used (i.e. faults are only distinguished by their type), I would point to the following two pieces of evidence that in my view contradict that view, and therefore indicates that we need a means of differentiating faults by name in WS-CDL:

1) WSDL1.1 spec:

 The 'name' attribute on the fault element is mandatory.
    <wsdl:portType name="nmtoken">*
        <wsdl:documentation .... />?
        <wsdl:operation name="nmtoken">*
           <wsdl:documentation .... /> ?
           <wsdl:input name="nmtoken"? message="qname">?
               <wsdl:documentation .... /> ?
           <wsdl:output name="nmtoken"? message="qname">?
               <wsdl:documentation .... /> ?
           <wsdl:fault name="nmtoken" message="qname"> *
               <wsdl:documentation .... /> ?

 The following syntax for an invoke, with embedded fault handlers, shows that the 'catch' elements have a mandatory 'faultName' attribute, whereas the type attribute is optional.
<invoke partnerLink="ncname" portType="qname"? operation="ncname"
        inputVariable="ncname"? outputVariable="ncname"?
     <correlation set="ncname" initiate="yes|no"?
<catch faultName="qname" faultVariable="ncname"?                         faultMessageType="qname"?>*
Received on Wednesday, 18 May 2005 15:17:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:08 UTC