I am on MX7 and I have the same problem. I changed to the full path in order to avoid it.
(I am on Unix and I'm using a lot of symbolic links, mappings, etc. - in my case this could be part of the problem).

Best regards,
Mihai Manuta


Cameron Childress wrote:
I'm just checking my sanity here....  These two calls should create an
object with the same datatype right?

<cffunction name="init" returntype="myObject">
   <cfreturn this/>
</cffunction>

<cffunction name="init" returntype="full.path.to.myObject">
   <cfreturn this/>
</cffunction>

And when this object is used in a cfargument tag with strict typing,
it both should "pass" the following type validation rule right?
<cfargument name="myObject" type="full.path.to.myObject"/>

We are getting an odd datatype mismatch error and I've thoroughly
confused myself trying to comprehend it.
----------------------------------------------------------
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]

Reply via email to