I don't understand the value of your solution... you're setting the
Application.settings from your Application.cfm, which loads them into
the application scope... then you are doing it again in the constructor
of the CFC, and assigning them to the application scope as well, which
will overwrite any existing application scope variables.
So it seems like you're still referencing the application scope
variables within the CFC, although you are loading them multiple times
for each CFC you load.
Also, you mention that you do this so you don't have to pass in
Application scope variables, but Application scope variables ARE
available to the CFC with no problem, so you don't have to pass them in
anyway.
I guess I'm just looking for a little more explanation as to why you
can't simply reference the application scope variables once they are
already initialized, because the CFC doesn't store its own version of
the application scope.
- Rick
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
