- From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
- Date: Mon, 15 Apr 2002 08:37:25 -0700
- To: "Marc Hadley" <marc.hadley@sun.com>
- Cc: "Martin Gudgin" <marting@develop.com>, "Christopher Ferris" <chris.ferris@sun.com>, <xml-dist-app@w3.org>
>OK, thanks. I guess that's OK provided there are no special processing >rules for faults other than: > >"An ultimate SOAP receiver MUST correctly process the >immediate children >of the SOAP body (see 5.3 SOAP Body). However, Part 1 of this >specification (this document) mandates no particular structure or >interpretation of these elements, and provides no standard means for >specifying the processing to be done." > >and that such processing may only occur after mu checking. Yes, I agree. >> "To be recognized as carrying SOAP error information, a SOAP message >> MUST contain exactly one SOAP Fault as the only child element of the >> SOAP body. A SOAP fault element information item MAY appear within a >> SOAP header block, or as a descendant of a child element information >> item of the SOAP body; but, in such cases, the element has no >> SOAP-defined semantics." >> > >I think this was added quite recently - no ? I thought the text you >quote was part of your proposal rather than spec text already. Its not >in the March 23rd snapshot. Do you recall which issue >resolution covered >this change, I can't see any mention in the change log ? Hmm, I found this in the Mar 23 snapshot [1] "A SOAP fault is used to carry error information within a SOAP message. "If present, a SOAP Fault MUST appear as a direct child of the SOAP body and MUST NOT appear more than once within a SOAP Body." Which in the April 11 snapshot was moved down a paragraph and now says: "To be recognized as carrying SOAP error information, a SOAP message MUST contain exactly one SOAP Fault as the only child element of the SOAP body. A SOAP fault element information item MAY appear within a SOAP header block, or as a descendant of a child element information item of the SOAP body; but, in such cases, the element has no SOAP-defined semantics." From what I can see, this was part of incorporating Noah's comments for part 1. Henrik [1] http://www.w3.org/2000/xp/Group/2/03/23/soap12-part1-1.37.html#soapfault [2] http://lists.w3.org/Archives/Public/xml-dist-app/2002Apr/0094.html
Received on Monday, 15 April 2002 11:37:57 UTC