> What do you want to do? Display the CFML error template or handle the error > from within the CFC in some way, for example returning nothing back to the > caller.
Even if you trap the error inside the CFC and return nothing or an error string back to the invoking page, you still need to test the value of your returned variable at that point to know whether to proceed or to display an error to the user. Running the invocation inside a cftry isn't much more work than examining the contents of your return to see if there's a problem (it also makes it more obvious to another developer who is working on your code later). Also, trapping the error inside the CFC assumes that you want to deal with it (ie sending it to a log) the same way each time; if you're creating a component for use in multiple applications then it's possible that you may want to handle errors differently for each. I'd assume (it's been a while since I have played with them) that if you try to consume a CF web service and you pass incorrect parameters then it will return an error message, which is what I'd want to happen (rather than have the CFC handle it for me). Is that not the case? --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
