Skip to main content
Ben Nadel at Scotch On The Rock (SOTR) 2010 (Amsterdam) with: Terrence Ryan and David Huselid and Alison Huselid and Claude Englebert and Ray Camden
Ben Nadel at Scotch On The Rock (SOTR) 2010 (Amsterdam) with: Terrence Ryan@tpryan ) , David Huselid , Alison Huselid , Claude Englebert@cfemea ) , and Ray Camden@cfjedimaster )

ColdFusion 9's NEW Operator Can Use Dynamic Class Paths

By on

Last week, I discussed the fact that in ColdFusion 9, the CreateObject() function no longer needs the "Type" parameter when creating ColdFusion components. ColdFusion 9 also introduced the New operator for component creation; but, I had stated that if you needed to create components with dynamic class paths, the CreateObject() method was great for this purpose. In the comments to that blog post, however, Edy Ionescu pointed out that the "New" operator in ColdFusion 9 can also use dynamic class paths. This kind of blew my mind and I needed to try it immediately.

To test this functionality, I created a simple ColdFusion component, Product.cfc, with a single public property, "Name." Then, I created a test script that instantiated said component using a class path variable:

<!--- Define the dynamic class path of the target component. --->
<cfset classPath = "Product" />

<!--- Use the NEW operator with the dynamic class path. --->
<cfset product = new "#classPath#"() />

<!--- Output the product's name. --->



As you can see here, I am using a quoted variable name to define the class path and then calling the "()" operator right after it. When we run this code, we get the following output:

Name: ProductName

This worked perfectly. Of course, using quoted values to create dynamic variable names in ColdFusion has been around for a long time. But, it's awesome to see this working in conjunction with the "New" and "()" operators! It looks like creating basic ColdFusion components in ColdFusion 9 has no more need of CreateObject(). I can't see that it offers anything over the New operator at this point.

Want to use code from this post? Check out the license.

Reader Comments


Totally agree, there is really no reason to use cfobject/createobject/cfinvoke when instantiating CFC's. There still useful for COM/Java/Webservices/etc. But for plain old CFC's, just use "new". ;)



For one, there's simply less to type; and the NEW operator is more in alignment with how other languages perform class instantiation. But, there is also some implicit wiring that happens. The NEW operator gives you control over which method is invoked as a constructor and what value that constructor returns.


Thanks my man!



Yeah, this is quality stuff! I really need to upgrade sooner than later.


ColdFusion is designed to allow for dynamic variable names in general. I think this is just part of that functionality; I don't think particular instance affects performance.