- From: Liu, Kevin <kevin.liu@sap.com>
- Date: Thu, 10 Mar 2005 17:05:21 +0100
- To: "Arthur Ryman" <ryman@ca.ibm.com>, <www-ws-desc@w3.org>
- Message-ID: <99CA63DD941EDC4EBA897048D9B0061D0B1C16AB@uspalx20a.pal.sap.corp>
Hi Arthur, Thanks for the contribution. I will incorporate your text to the primer. Best Regards, Kevin _____ From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] Sent: Thursday, Mar 10, 2005 07:30 AM To: www-ws-desc@w3.org Subject: Proposed Primer Text to Show Fault Reuse and Fault Codes 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 16:06:10 UTC