Alexander Sherwood wrote:
Say the return type is a struct. What do you do, put the error type as the key name and the
error message as the key value?
See my
You could wrap all calls to the service in a "facade" CFC that CFTRYs to
invoke the requested service and CFCATCHes exceptions, translates them, and return and nice little XML message?
This may be on option. I haven't thought of that yet. How could I figure out all possible combos of errors returned from invalid types. I could pass a type differant than the type attribute to see what the message would be. But I really can't trust cf to return only those. I've seen some wack errors coming from CF.
This is probably the easiest and simplest way to achieve what I'm looking to do. Thanks for bringing this one up. Hopefully it will work in all situations.
----------------------------------------------------------
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]
