18
Replies
The process has been this way for nearly a decade.
By @nak33
I understand.
However, it is worth pointing out that the ColdFusion application server has changed a lot in recent years. Generally for the better.
Though ColdFusion promises backward-compatibility, it cannot always fulfill that promise.
Let me know what you discover.
By @nak33
I have been able to show that, if you use code of the form
<cfcomponent>
<cfobject />
</cfcomponent>
it can lead to problems.
The demo consists of 5 files. Create a test directory under the web root and place the 5 files in it.
<!--- Application.cfc --->
component {
this.name = "cf_forum_Nak33Test";
this.sessionManagement = true;
boolean function onApplicationStart() {
return true;
}
}
<!--- Test1.cfc --->
<cfcomponent>
<cfobject component="test2" name="t2" />
<cfset this.t2 = t2>
</cfcomponent>
<!--- Test2.cfc --->
<cfcomponent accessors="true">
<cfproperty name="p1">
<cfproperty name="p2">
<cffunction name="init" returntype="any">
<cfset variables.p1="I am property p1 of Test2 CFC">
<cfset variables.p2="I am property p2 of Test2 CFC">
<cfset variables.properties = {property1="#p1#",property2="#p2#"}>
<cfreturn this>
</cffunction>
</cfcomponent>
<!--- testPage1.cfm --->
<cfset test1Obj = new Test1()>
<cfdump var="#test1Obj#" >
<!--- testPage2.cfm --->
<cfset test2Obj = new Test2()>
<cfdump var="#test2Obj#" >
Now, on to the test.
Launch the page testPage2.cfm, followed by the page testPage1.cfm. You should get something like
Result of the test: using <cfobject> in the constructor code of Test1 creates an instance of Test2 in which the value of the instance properties p1 and p2 is null. That is incorrect. Test2.cfc is defined such that every instance of it will contain a value for the properties p1 and p2.
AdChoices