oh....so thats why they keep writing all of these standards. I guess I actually have to read them.
Thanks -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:53 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Exception handling strategy question There are four defined reasons to return a SOAP fault [1]: - VersionMismatch: the request didn't specify the correct SOAP namespace - MustUnderstand: a SOAP node did not understand a SOAP header that said mustUnderstand='1' - Client: the request failed either because it was malformed or contained invalid data - Server: the request failed because of some type of server error Remko's example requires an error code of Client. The error report should be returned in the fault <details> element. As long as you have Java on both sides of the wire, the SOAP system on the client should be able to simply rethrow the original exception (assuming that it has the exception class installed). But if you intend to support non-Java clients, you should map your various exceptions to specific SOAP fault messages. [1] http://www.w3.org/TR/SOAP/#_Toc478383510 Regards, Anne
