Web service have a concept of exceptions, though they're called "faults". That's the best way to get exception information back to a client, because it doesn't put any funny restrictions on your return type, and its a standardized way to deal with error information. Just make sure that you include reasonable information in your exception messages so that a machine, or at least a human, can figure out what went wrong and fix it.
cheers, barneyb ----- Original Message ----- From: Ian Skinner <[EMAIL PROTECTED]> Date: Thu, 16 Sep 2004 16:10:28 -0700 Subject: [CFCDev] CFC - Web service error handling To: [EMAIL PROTECTED], [EMAIL PROTECTED] I have recently written my first, simple webservice and once I learned the importance of white space, ie have none; in any application.cfm file located in the same dirctory with the webservice CFC, all went well. My question is what is the best pratice to handling errors in a webservice? Other then have none, of course! It seems to me, on first glance, to be a bit of a tricky subject? What information, if any, about an error do you provide to a consumer of the webservice. And if you do provide information, how do you do this, if you are specifing the return type to be something incompatable with returning useful error information? -------------- Ian Skinner -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com Got GMail? I can help. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
