Re: Invoking components, methods and storing instance in application scope

2009-09-27 Thread Sean Corfield
On Sun, Sep 27, 2009 at 6:22 PM, Kevin Pepperman wrote: > Using an init() method, although not required, is considered best practice > in the CF world for initializing components because cfc's don't have true > constructors like JAVA (yet). Just a couple of points to elaborate on this... We use

Re: Invoking components, methods and storing instance in application scope

2009-09-27 Thread Kevan Stannard
Hi Tony, you make like to take a look at http://learn.objectorientedcoldfusion.org/wiki/The_Init()_Function > instances of an object. I have also seen quite a bit about using > init() in every component but am not sure why I would do this if I > just want to call a method from the application

Re: Invoking components, methods and storing instance in application scope

2009-09-27 Thread Kevin Pepperman
Hello Tony. I am no expert, But I do know about where you are at right now, and I also know what it took for me to learn it, so I will give it a shot to at least set you off in the right direction. Using an init() method, although not required, is considered best practice in the CF world for in

Invoking components, methods and storing instance in application scope

2009-09-25 Thread Tony Bentley
I am building an application where I want to eliminate instantiating the same component more than once per application. I thought it would be a good idea to setup all of the methods through the application scope: application.getters = createObject("component","cfc.GetterQueries"); This way I a