If you mean nice warm fuzzy messages that an end user will understand then I
agree with you, but if you mean useful informational messages that a
developer attempting to use your webservice can understand then I strongly
disagree.
Then it seems we are all in accord here: messages displayed to screen cannot be modified nor influenced by the developer of a webservice; messages delivered to the consuming program (and, ergo, the developer of the consumer) should have a good ability to be customized. Some seem to disagree as to whether this ability exists for this case.
I am planning on developing some webservices soon. In the interest of debugging, how would one go about examining the SOAP call made by CF, and the SOAP response that comes back? I don't mean the values as parsed; how would one take a peek at the XML that changes hands? As the case in point, I don't know whether the default SOAP Fault message for a type mismatch is adequate for my purposes.
Tips?
--
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]
