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, Tricia.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 = "Tricia" />
- <!--- Use the NEW operator with the dynamic class path. --->
- <cfset girl = new "#classPath#"() />
- <!--- Output the girl's name. --->
- Name: #girl.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:
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.
Looking For A New Job?
- Full Stack Angular/Rails Engineer @ newly funded Health-IT startup at Dorsata
- Part-time remote DBA needed at Bridge
- Senior Developer Wanted for International Cloud Company at Giva, Inc.
- ColdFusion Developer - jQuery, PrimeUI, ORACLE DB at ComSpec International, Inc.
- Jr. ColdFusion Developer - Full Time / Telecommuting is ok. at InterCoastal Net Designs
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". ;)
Yeah, I'm really like the New operator a lot. Now, I just need to upgrade more of my servers!
Great post. Thanks for sharing this information about the NEW operator in ColdFusion 9.
Hi Ben, what is benefits using NEW instead of createObject?
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!
Thank you! That is great to know.
I wonder if there are any performance implications for creating objects this way.
@Jason, I think u still need cfinvoke, unless you're ok with Evaluate().
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.
Are you aware of any documentation for how the new operator resolves the location of cfc's?
It's a shame we still cant go:
Now it looks CF9 is following its parent tech Java.