If it ever were to change, I'd wager 30 seconds in global find and replace would easily fix the issue. Or you could create your own dummy class named WEB-INF.cftags.component and put it somewhere in the component "class path".
Roland -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Carabetta Sent: Saturday, December 17, 2005 2:34 PM To: [email protected] Subject: Re: [CFCDev] CFC name vs. full path in returntype attribute William, I just blogged about this very question because I wasn't sure how "safe" it would be from a forwards-compatibility standpoint. The consensus was that the WEB-INF.cftags.component returntype is safe across versions of ColdFusion MX, including Macromedia vs. New Atlanta. I would use that instead of "any." As Sean noted in one of his comments to my entry, a nice enhancement in Scorpio would be to add a returntype="component" option. http://www.cbetta.com/blog/index.cfm/2005/12/9/return-type-for-returning-cfc -instances Regards, Dave. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
