- From: Marc Hadley <Marc.Hadley@Sun.COM>
- Date: Fri, 18 Mar 2005 09:19:03 -0500
- To: Martin Gudgin <mgudgin@microsoft.com>
- Cc: Mark Baker <distobj@acm.org>, David Hull <dmh@tibco.com>, public-ws-addressing@w3.org
On Mar 17, 2005, at 6:07 PM, Martin Gudgin wrote: > > A fault is any message for which the following XPath expression > evaluates to true; > > /soap:Envelope/soap:Body/soap:Fault > > See[1], specifically; > > "To be recognized as carrying SOAP error information, a SOAP message > MUST contain a single SOAP Fault element information item as the only > child element information item of the SOAP Body" > Picky, but I don't think the XPath captures "the only child EII of the SOAP Body", e.g. the following satisfies the XPath but not the complete criteria: <soap:Envelope> <soap:Body> <foo:bar/> <soap:Fault> ... </soap:Fault> </soap:Body> </soap:Envelope> Marc. > > [1] http://www.w3.org/TR/soap12-part1/#soapfault > >> -----Original Message----- >> From: Mark Baker [mailto:distobj@acm.org] >> Sent: 17 March 2005 14:56 >> To: Martin Gudgin >> Cc: David Hull; public-ws-addressing@w3.org >> Subject: Re: A minor question >> >> On Thu, Mar 17, 2005 at 02:16:11PM -0800, Martin Gudgin wrote: >>> >>> I've not seen an answer to this question, so here goes; >>> >>> A fault is just a reply. So the relationship would be reply. >> >> +1 >> >>> You can >>> tell it's a fault because SOAP defines a fault message very >>> specifically. >> >> Actually, it doesn't. But let's not go there. 8-) >> >> http://lists.w3.org/Archives/Public/xml-dist-app/2002Mar/0007.html >> >> Mark. >> > > --- Marc Hadley <marc.hadley at sun.com> Web Technologies and Standards, Sun Microsystems.
Received on Friday, 18 March 2005 14:19:01 UTC