Grazie mille per l'aiuto, Massimo.
But this isn't happening. I get the correct results every time. Not that I want my stuff to break, but if I can't understand the problem then how can I know that I'm avoiding it in the future?
I guess this is a matter of not being able to reproduce the problem, not understanding it, right?
Well, I understand what people are saying, I think. The concern boils down to "if the dot notation path is the same for two different CFCs, then you might be calling the wrong CFC."
I have no idea about your configuration.
Do you have both D:\web\test_app_one\ and D:\web\test_app_two\ as virtual servers?
They are two virtual hosts on the same server (Apache 2.0.46), same IP address (http/1.1 to distinguish by host header), and under "Caching" in the CFMX Administrator we have deselected "Cache web server paths".
All sites (a couple dozen) are under D:\web\. The web root for "sitename" would be D:\web\sitename\
We are developing a new model for websites in which all non-web-accessible files (CFCs, custom tags, etc.) for a site is in its "application" folder: D:\web\sitename\application\ (we seal that off with an Apache directive to "Deny from All" on that directory). This, we hope, will help it be more portable.
What happens if the CFCs aren't below the folder hierachy of the calling template like: D:\web\test_app_one\application\objects\crossover_test.cfc D:\web\test_app_one\anotherdir\calling.cfm
On your suggestion, I moved the test cfm pages to a subdirectory off the root; I didn't change their call to "application.objects.crossover_test" which is the path from the webroot. It all still works correctly -- the problem does not get triggered. Here are the files I'm using:
D:\web\test_app_one\application\objects\crossover_test.cfc D:\web\test_app_one\crossover_test\crossover_test.cfm D:\web\test_app_two\application\objects\crossover_test.cfc D:\web\test_app_two\crossover_test\crossover_test.cfm
Since D:\web\ is the CF root (I may be wrong), how do you make this working: <cfinvoke component="application.objects.crossover_test" ?
Right. The webroot is D:\web\test_app_one\ and an Apache alias (like a "virtual directory" in IIS) links calls to /CFIDE to our CFRoot at C:\apps\CFusionMX\wwwroot\CFIDE (we need that set up to make Flash Remoting work, evidentally).
Do you have any mapping or custom tags path defined?
Only one mapping in the CF Administrator:
/CFIDE -> D:\apps\CFusionMX\wwwroot\CFIDE
So, as far as I can tell this test ought to trigger the problem unless:
a) CF is including the directory paths outside of the root (ie, "test_app_one" and such) in its cached class names; or
b) CF is caching the classes on a per-application basis; or
c) CF isn't caching the classes at all and I just can't tell
Any insight would be greatly appreciated. As I alluded to, we are developing a new standard way for us to build CF sites and applications, and I would hate to standardize on something that will break down the road.
--
Ben Curtis
WebSciences International
http://www.websciences.org/
v: 310 478 6648
f: 310 235 2067----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
