- From: Asir Vedamuthu <asirveda@microsoft.com>
- Date: Wed, 4 Nov 2009 02:54:23 +0000
- To: Gilbert Pilz <gilbert.pilz@oracle.com>, "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
- CC: Doug Davis <dug@us.ibm.com>
- Message-ID: <4F4942E980BD7147AE7F7D3DCB9CBA9F044049E7@TK5EX14MBXC132.redmond.corp.microsoft.>
What does that mean to issue 7911? Regards, Asir S Vedamuthu Microsoft Corporation From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Gilbert Pilz Sent: Tuesday, November 03, 2009 12:01 PM To: public-ws-resource-access@w3.org Cc: Doug Davis Subject: RE: issue 7911 and BP WG (was [wsi_wsbasic] [NEW ISSUE] use of SOAP Sender faults]) FYI, the WS-I BP WG today accepted the following issue related to 7911. It was assigned issue numbers BP20159 (for BP 2.0) and BP12073 (for BP 1.2). - gp -------- Original Message -------- Subject: [wsi_wsbasic] [NEW ISSUE] use of SOAP Sender faults Date: Mon, 2 Nov 2009 13:54:43 -0500 From: Doug Davis <dug@us.ibm.com><mailto:dug@us.ibm.com> To: wsi_wsbasic@mp.ws-i.org<mailto:wsi_wsbasic@mp.ws-i.org> SOAP defines a "Sender" (1.2) and "Client" (1.1) fault but isn't very explicit about when to use it. Likewise, when a receiver gets a message that isn't properly formed w/o clear guidance on what fault should be generated its possible that there could be an interop problem when a client is expecting one type of fault when the server sends something different. This issue was discovered during the proceedings of the W3C WSRA WG. Proposal: Add the following to section 3.4 in BP 1.2 and BP2.0. 3.4.2 SOAP Client Faults (BP 1.2) / 3.4.7 SOAP Sender Faults (BP 2.0) When a RECEIVER receives an incoming message that is ill-formed or does not contain adequate information to be properly processed, the RECEIVER has two options. First, if the specification that defined the incoming message defines a fault that is specifically focused on the particular error condition found within the message, then the RECEIVER needs to use that specification specific fault. However, if the specification does not define a fault then to ensure interoperability this Profile requires the use of the SOAP Client/Sender fault. Rxxx Upon detection of a message that is not properly formed, or is missing sufficient information to be properly processed, unless the specification that defined the incoming message defines a fault that is specific to the error condition, the RECEIVER MUST generate a SOAP Client/Sender fault. thanks -Doug ______________________________________________________ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | dug@us.ibm.com<mailto:dug@us.ibm.com> The more I'm around some people, the more I like my dog.
Received on Wednesday, 4 November 2009 02:55:04 UTC