Creating a "custom" mechanism for
indicating errors is only going to piss off the people who know what they're
doing, and expect to get a Fault message back if there is a problem.
I agree. It's much easier to wrap a WS call in try/catch and handle the error in a consistent manner than to have to test every single return from every single WS call to see whether it was bogus or not. SOAP is a standard and SOAP Faults are part of that standard. Coding around them leads to consumers having to treat your WS different to the majority - that would certainly frustrate me and I'd go off looking for a more standard WS.
Sean A Corfield -- http://www.corfield.org/blog/
"I have always wished that my computer would be as easy to use as my telephone. My wish has come true - I no longer know how to use my telephone."
-- Bjarne Stroustrup
----------------------------------------------------------
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]
