I think it pertains to scoping/visibility of "variables.*" from within
CFCs... I came across that one as well (except I was creating the
method in fusebox.init.cfm). You can assign the method to the request
scope and you should be able to access your App.cfc method from your
model:

<cffunction name="foo">
...
</cffunction>
<cfset request.foo = foo />

My guess is this probably resembles your workaround :]

On Mon, Jun 22, 2009 at 5:15 PM,
the_one_true_dave_anderson<dave@...> wrote:
>
>
> This is an elusive problem for which I've already instituted a workaround,
> so it's not terribly urgent, but quite vexing nevertheless...
>
> I have a FB5.5 app (with an xml-less config), and there's a function in my
> App.cfc called isProduction() that returns a boolean value. I had been
> setting an application.mode variable (to 'prod' or 'dev') based on the value
> returned by this function, but recently discovered (!) that I could call
> isProduction() from pretty much anywhere. However, after recently deploying
> updates to a testing environment, I found that the function would not
> execute in one of my Model cfc's -- though worked fine in display templates.
> I did/do not have this problem on my local dev environment.
>
> Any ideas why the Application.cfc's function would work in a display
> template but not in an implicitly-loaded FB Model cfc?
>
> Thanks!
>
>