Bryan,
I think you're missing David's point. You *cannot* display a friendly error message to the person consuming your webservice, not because you shouldn't but because webservices are not displayed. XML changes hands, and in the end your "friendly" error messages are the same sort of SOAP response as a native SOAP error message--they are both XML to be parsed and dealt with by the consumer.
If the consumer is running CF, they will see their own CF error message.
If .NET, they will see the .NET error message that they coded.
If a newsreader, Sherlock, Big Bob's SOAP-O-Matic--they will see the error message native to those programs.
If the person coding the consuming program wants to see something more friendly, then they need to code it or give you access to their program--nothing your SOAP response can contain will inherently display anything, much less something friendly.
Your other concerns, such as logging the error on your end, seem to be a valid reason to pursue this sort of control, but friendly error messages are impossible no matter how you code them.
On Jun 3, 2004, at 1:56 PM, Bryan F. Hogan wrote:
Whatever
David Ross wrote:
This is up to the consumer/client!!!! You, as author of web service,
have no business worrying about what is "shown" to the end user. If the
client supplied invalid arguments, the client should take on the job of
inspecting the SOAP fault to see what went wrong.
--
Ben Curtis
WebSciences International
http://www.websciences.org/
v: (310) 478-6648
f: (310) 235-2067----------------------------------------------------------
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]
