If CFCs were EJBs, you would have external config info that you would
look up using JNDI (or something, I'm not quite up to snuff on J2EE).
Let's say I am careful and create well named variables like...
request.<cfcname>.datasource = "MyDatasource";
request.<cfcname>.timeout = 300;
etc, all in one file called <cfcname>.cfm that is included in
application.cfm. Contract with the developer is you have to include
<cfcname>.cfm in your application.cfm before calling the CFC. Am I such
a bad guy?
I guess worst case scenario is Macromedia decides not to support it one
day, but I haven't heard anything about that. It's just such a pain if
there's 10 variables in your app that are required by 10 different CFCs,
passing them in as args to the constructor seems awkward.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
