I'm not sure if the real problem is something in CF or something in the way the environment is set up, but whatever the case, using the full path solves the problem.
On 12/15/05,
Sean Corfield <[EMAIL PROTECTED]> wrote:
On 12/15/05, William Langshaw <[EMAIL PROTECTED]> wrote:
> I am wondering what kind of ill-effects can arise from NOT using the
> CFC's complete type (path) in the returntype attribute. That is, using
>
> Returntype="Person"
>
> As opposed to
>
> Returntype="com.sitename.foobar.Person"
I don't know what ill-effects can arise from using the shorter form. I
tend to use the shorter form for returntype= and cfargument type= so
that a CFC can be picked up and dropped into another directory without
code changes (obviously the same cannot be said for returntype= and
cfargument type= attributes that reference a different type).
--
Sean A Corfield -- http://corfield.org/
Got frameworks?
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
----------------------------------------------------------
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]
