Sounds like we could use a 'throwOnError' attribute for either the cffunction or cfargument tag, maybe both.
Why? What would you expect to happen if you said throwOnError="false"? How would you handle the error and why would that be different from doing the following:
<cfargument name="arg" type="any" required="true" />
<cfif isNumeric(arguments.arg)>
... normal processing ...
<cfelse>
... error processing ...
</cfif>Something that works the same as the cfhttp attribute. Then you could have
the wsdl specify the required parameter type and do the checking yourself in
a webservice situation.
But if you are calling it as a web service you *can* catch and handle the error:
<cftry>
<cfset ws.callMethod("not a number") />
... continue with processing ...
<cfcatch type="any">
... do something with the error ...
</cfcatch>
</cftry>Sean A Corfield -- http://www.corfield.org/blog/
"There are no solutions, only trade-offs." -- Thomas Sowell
----------------------------------------------------------
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]
