Yes you can work fine by setting it to 'any', and then living with developer guidlines to ensure the right object is passed through, but I personally find this kinda cludgy.
Just my opinion of course.
Mark
On 3/17/06, Cliff Meyers <[EMAIL PROTECTED]> wrote:
Alternatively you can just put the component name in the cfargument
type attribute or cffunction returntype attribute. So instead of
"com.company.app.User" you could just list "User" instead. This gives
you some flexibility as to the path (aka "package") of the CFC is
although if you have two "User" cfcs in different packages they would
both be valid which you probably don't want. I don't see that as a
major issue though. I'm not sure what the implications of this
approach are for CFCs that inherit from another CFC though.
No matter which way you go, I would strongly consider getting a local
development environment set up. The upfront investment will save you
time and headaches in the long run.
-Cliff
--
E: [EMAIL PROTECTED]
W: www.compoundtheory.com
ICQ: 3094740 ----------------------------------------------------------
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]
