W3C home > Mailing lists > Public > www-ws-desc@w3.org > March 2005

Proposed Primer Text to Show Fault Reuse and Fault Codes

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Thu, 10 Mar 2005 10:29:47 -0500
To: www-ws-desc@w3.org
Message-ID: <OF2542D240.3DA858F2-ON85256FC0.005311BE-85256FC0.00551D4F@ca.ibm.com>
In fulfillment of my Action item dated 2005-01-20 - 

The following text should be added to the Primer, section 5.1.1 Binding 
Faults:

"Faults are very similar to messages and can be viewed as a special kind 
of message. Both faults and messages may carry a payload that is normally 
described by an element declaration. However, WSDL treats faults and 
messages slighly differently. The messages of an operation directly refer 
to their element declaration, however the faults of an operation 
indirectly refer to their element declaration via a fault element that is 
defined on the interface. 

The reason for defining faults at the interface level is to allow their 
reuse accross multiple operations. This design is especially beneficial 
when bindings are defined since in bindings like SOAP there is additional 
information that is associated with faults. In the case of SOAP, faults 
have codes and subcodes in addition to a payload. By defining faults at 
the interface level, common codes and subcodes can be associated with 
them, thereby ensuring consistency accross all operations that use the 
faults."

There is the start of an example in section 5.2, Example 5-1. This should 
illustrate the use of SOAP fault codes.

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
intranet: http://labweb.torolab.ibm.com/DRY6/
Received on Thursday, 10 March 2005 15:30:17 GMT

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