CFC - to init or not to init

Thanks for the answers. In the end I've decided NOT to include an init and simply declare this variables at the top of the components, so that i can easily change their properties, if required, after instantiation e.g. instancename.DevDSN instancename.TestDSV.

Paul,

Wanted to let you know that your attachments/code samples did not post with the topic.

There are a few reasons that it's advisable to create an init method for your CFCs. A big reason, perhaps the most significant one, in favor of using init() is to initialize constants and other variables for your CFC as well as to return an instance of the CFC to the calling page.

Another reason is that, when you don't use it, ColdFusion will invoke init() once you call a non-static method of the CFC. In short, CF will call init() to initialize it, anyway (there could be a minor performance gain for using init() when you setup the object rather than waiting for CF to do it).

Yet another reason for init() is that, if you want to have persistent access to the CFC, by storing it in the session scope for example, you must use init() because it returns a reference to an instance of the object where other approaches (cfobject, etc.) do not.

One interesting note about CFCs is that you don't need to explicitly call init() when you create an object from your CFC. You may also add an init() call to the constructor area of a CFC (typically this code is placed between the opening cfcomponent tag and the first cffunction tag) and that will get called when you instantiate the CFC:

<cfcomponent>

     <cfset init() />

     <cffunction name="init">... code ... </cffunction>

</cfcomponent>

Another interesting thing about CFCs is that the init 'method' is not really a method; rather, it's an identifier, related to how ColdFusion and Java interact. When you use (create) Java classes in your CFML, you need to use init() to call the constructor of the Java class. This isn't really relevant for a lot of us but it explains why it's called init() and not something else.

For me, most applications I build need both to initialize an object with special values (unique ids, etc.) and to persist several objects/CFCs across the application. As such, I find that staying in the habit of using init() works well for me.