@Dean, Looked into this a bit further on CF10.
root - Application.cfc - ApplicationProxy.cfc (extends Application) - cfc-folder - - Application.cfc (extends ApplicationProxy) - - myCFC.cfc This does not work without the cfc/application.cfc having extends="root.ApplicationProxy", where 'root' is a CF mapping. As you said, CF will search from the application root downward on the file system. Since there is an Application.cfc in the cfc folder, it would start there and not find the ApplicationProxy in the directory above. This would work if the actual root directory was cfusion/wwwroot, or maybe if both application.cfc had the same applicationName and the ApplicationProxy was used/cached in /root app somehow before /root/cfc was initialized. If you use a CF mapping the proxy is really not even necessary, as this does work. /cfc/application.cfc --------------------------------- <cfcomponent extends="root.application"> Cheers, Byron On Wed, Jan 28, 2015 at 3:44 PM, Dean Lawrence <dean...@gmail.com> wrote: > > Byron, the ApplicationProxy.cfc needs to be in the root directory along > with the main Application.cfc. When you extend a CFC, CF will first look in > the same directory to see if that CFC exist. If it doesn't CF will start > looking for the CFC from the application root down. So by simply adding > extends="ApplicationProxy" to the Application.cfc within the /cfc > directory, CF will find the ApplicationProxy.cfc in the root, which in turn > finds the Application.cfc in the root. No mappings are needed. > > T ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:360039 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
