Application.cfc Feature Request

Andrea,

Good point. I should have included an example.

Let's say that I have a variable that I want set for every file in a folder. Perhaps, I want to indicate that each file in the folder is in the "About" section. I might want to do:
<cfset Section = "About">

Instead of including that in each file, it would be easier to put it in an Application.cfm in that folder. I still need the parent Application.cfm to execute though, so I add <cfinclude template="../Application.cfm">

Now, I know that this problem can be circumvented altogether by other framework or architecture decisions, but that is hardly the point. I want ColdFusion to make my life easy.

Steve, have you tried to extend an Application.cfc to a parent with a cfmapping in place? The reason I ask is because of how Fusebox 5 works. I have a Fusebox 5 application with its own Application.cfc. When you open that component, it extends fusebox5.Application. I have a mapping for fusebox5 in my CFAdministrator and each method so that CF knows how to find the Fusbox 5 core files and such. Within the application's Application.cfc, all methods start with a call to super():

Craig,

It is probably a personal thing, but I really don't like mappings.

In my case, I want to be able to just drop a folder in the site and *not* have any requirements for the site that the folder is being dropped into for it to work. This is just really important to me and anything that gets in the way of that is a frustration.

John,

That does make sense. I actually gave an example in the comments. Specifically, I just want a custom onMissingTemplate applied to one folder.

I don't want to have to know what framework is or isn't being used or use a framework-specific answer. It just really seems like CF should make this easy. Isn't that the point of CF, after all?

I agree with john,
I usually add simple handler method inside application.cfc methods and handle things differently. My application.cfc is 99% always the same file.

you don't need to use that applicationproxy trick in order to extend the application.cfc. if you want to extend the root application.cfc in a subdirectory, just use:

cfcomponent extends="/.application"

don't know why it didn't work for you. i'm using this exact trick in a current application i've written. maybe I was clear on the tactic. you can your root application.cfc from any application.cfc that is in a subdirectory by using the extends="/.application":

<!--- this application.cfc live in a subdirectory from the root --->
<cfcomponent extends="/.application">