- From: Eamon O'Tuathail <eamon.otuathail@clipcode.com>
- Date: Wed, 18 Jul 2001 22:11:34 +0100
- To: "David Crowley" <dcrowley@scitegic.com>
- Cc: <xml-dist-app@w3.org>
From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On Behalf Of David Crowley >> SOAP errors are communicated with SOAP Fault. HTTP errors are >> communicated with HTTP status codes. David, FYI, in the SOAP over BEEP binding, this same issue arises - SOAP have SOAP Fault errors, and what transfers it, BEEP, has BEEP ERR messages. The solution there was to use BEEP ERR messages for things that went wrong at the BEEP level only. BEEP considers the SOAP envelope it carries as opaque, and does not peek inside. So it does not know, and does not need to know, that a particular envelope actually contains a SOAP fault. In most implementations, the pieces of code that handle the transfer protocol and the SOAP processing are distinct, so as you suggest, having distinct errors for them seems appropriate. Eamon
Received on Wednesday, 18 July 2001 17:08:17 UTC