Well, it's different than I thought. I think, at one time, we had the
component in the application scope, but took it out because of similar
errors.
Now, the component is only created on the few pages where it is
required. Still, we have the intermittant errors.
Here is one of the error messages:
Could not find the ColdFusion Component or Interface GlobalFunctions.
Ensure that the name is correct and that the component or interface
exists. <br>The error occurred on line 22.
It is called by:
<cfset globalFunctions = createObject("component", "GlobalFunctions")>
It may be an issue with component instantiation because this works 99%
of the time, but fails without any explanation.
Thanks,
Mike
-----Original Message-----
From: Adrian Lynch [mailto:[email protected]]
Sent: Thursday, June 18, 2009 8:43 AM
To: cf-talk
Subject: RE: Application Scope Problem
How are you setting the component in the app scope?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Want to reach the ColdFusion community with something they want? Let them know
on the House of Fusion mailing lists
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:323638
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
