Sean Corfield wrote: > <cffunction name="sendFax" returntype="numeric" access="remote" > output="false"> > <cfargument name="userID" type="any" required="false" > wsdltype="numeric" wsdlrequired="true" /> > <cfargument name="faxNumber" type="any" required="false" > wsdltype="numeric" wsdlrequired="true" /> > <cfset var status = 0 /> > ... > <cfreturn status /> > </cffunction>
You could actually do this right now. The CF engine will just ignore the extra attributes, so you can leave them there all the time. When it comes time to generate the WDSL, use a global search and replace to covert the 'type' and 'required' attributes to some unknown names (like 'type_' and 'required_'), and do another to convert 'wsdltype' to 'type'. Generate your WSDL for your services, and save it, and then reverse the search and replaces. Granted, it's not a particularly elegant solution, but if the API you're implementing is as complex as you've made it out to be, chances are it's not going to change all that much. Though I suppose you could automate the whole process with a CF script if you really wanted. Cheers, barneyb ---------------------------------------------------------- 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]
