if you are refering to business logic that happens after the request has been accepted I would say that the best way is to return some type of error report. I could be wrong but it seems like soap fault should only be thrown if there was a conformance issue. Someone please correct me if I am wrong.
--George -----Original Message----- From: remko de knikker [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: Exception handling strategy question when implementing a web service and a ws client, what is the general design principle for exception handling, when 1. when user entered a non-valid input value, for instance it doesn't exist in the database? Do I simply through a SOAPFault or is it better to append my own <doesnotexist> tag? 2. as a client, do I catch an xxxxException/Fault, do I look for the soapenv:Fault tag or do I have to look the webservice specific <wserror> tag?? What is the best design strategy here?? thanks, r
