[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Handling Multiple Service Responses
Fraser Goffin writes: > I considered just using 2 response types, success and SOAP Fault, > but I think it might be better to reserve SOAP Faults to non > business messages that we don't really want a caller to have to be > concerned with (other than the fact that the invocation failed). You are of course free to do this if it meets your needs. I do note that the SOAP Primer [1] says: "The SOAP fault model (seehttp://www.w3.org/TR/2007/REC-soap12-part1-20070427/#procsoapmsgs) requires that all SOAP-specific and application-specific faults be reported using a single distinguished element, http://www.w3.org/TR/2007/REC-soap12-part1-20070427/#soapfault, carried within the env:Body element. " Note that this primer is non-normative, and I think the above advice goes somewhat beyond what a strict reading of the normative parts of the Recommendation require. Still, it does signal quite clearly that the authors of SOAP intended that SOAP Faults be used to reflect errors insofar as practical. Noah [1] http://www.w3.org/TR/soap12-part0/#L11549 -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 --------------------------------------
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|