It sounds strange that you can have a cfc include a function that can
be called, but not appear in the CFC Explorer or the GetMetaData
function (which I guess CFC Explorer uses). So it's possible that the
GetMetaData could be reading the file to get the private function data
as a cfdump of an obj
g/blog/
-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Chris Velevitch
Sent: Monday, October 16, 2006 1:06 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: CFC Explorer and Application.cfm
On 10/16/06, Charlie Arehart <[EMAIL PROTECTED]
On 10/16/06, Charlie Arehart <[EMAIL PROTECTED]> wrote:
> Fair enough. How about being more explicit regarding where you're using the
> application variables, such that the CFC explorer fails? It's beddy-bye time
I'm doing cfincludes and I'm using the application variables to define
the location
al Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Chris Velevitch
Sent: Monday, October 16, 2006 12:32 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: CFC Explorer and Application.cfm
On 10/16/06, Charlie Arehart <[EMAIL PROTECTED]> wrote:
>
On 10/16/06, Charlie Arehart <[EMAIL PROTECTED]> wrote:
>
> Chris, did this response make sense for your situation?
Not really.
If the CFC Explorer is "invoking" my cfc, then why isn't the
Application.cfm be called first like any other cfc invocation? This is
where my variables are being initial
: [cfaussie] Re: CFC Explorer and Application.cfm
I would guess "no". The CFC explorer is a CFML app running under the CF
Admin directory, and it simply invokes your CFC. If you're expecting code to
have run before the CFC is invoked, it will not have run it. This is perhaps
one of t
I would guess "no". The CFC explorer is a CFML app running under the CF
Admin directory, and it simply invokes your CFC. If you're expecting code to
have run before the CFC is invoked, it will not have run it. This is perhaps
one of the reasons that there's a recommendation (best practice) against
