Just checking my knowledge here, about extending an application.cfc into a subfolder - Is using an empty proxy.cfc in the root folder that extends the application.cfc still the way to go? (as outlined here)

I was following the logic in Gregory's Blog, until I saw this:

<cfcomponent sessionmanagement="yes" clientmanagement="yes">

I had expected the usual

<cfcomponent>

<cfset this.sessionmanagement="yes" >

<cfset this.clientmanagement="yes">

yeah, I wouldn't do things exactly the same

Yep, we had to do almost this exact thing when migrating from Application.cfm Our Taffy endpoints used to

include Applicaiton.cfm

in the onREquestStart, now they...

function onRequestStart( targetPath = "" ) {
		AppProxy = new ApplicationProxy()
		AppProxy.onRequestStart()
		return super.onRequestStart( targetPath );
	}

@Dean thanks for the confirmation!

On checking on the web, I can see that such "proxy" solutions for extending Application.cfc go way back. For example, Dan Short published "Extending the root Application.cfc" in April 2005. I wonder whether you can now solve the problem in a simpler, neater way. The following procedure seems to work: on Adobe ColdFusion 2023, at least: 1. In the ColdFusion Administrator, go to _Server Settings > Mappings, and a_dd the mapping with Logical Path = /appRoot and Directory Path = C:/ColdFusion2023/cfusion/wwwroot 2. Begin the code of the Application.cfc of the subfolder with:

<cfcomponent extends="appRoot.Application">

@bkbk never thought to do it with a mapping - interesting approach! Thanks for sharing

@bkbk not sure I understand your comment, but what I wrote is what we are doing. We dont want to extend the root Application.cfc for reasons, but we do need the variables that

onRequestStart

handles in it.

@Dean, what I mean is, if your local Application.cfc extends ApplicationProxy.cfc, then ColdFusion/Lucee will automatically instantiate ApplicationProxy.cfc. That is, ColdFusion/Lucee will evaluate

new ApplicationProxy()

under the bonnet. Inheritance is transitive: if your local Application.cfc extends ApplicationProxy.cfc, and ApplicationProxy.cfc extends the root Application.cfc, then your local Application.cfc extends the root Application.cfc. I am therefore confused by your statement that you "dont want to extend the root Application.cfc".

Our local Application.cfc doesnt extend ApplicationProxy, it instantiates it as ApplicationProxy

Ah, I see.

I need to update and rewrite this article. It got corrupted when I migrated from Hostek to Media3 a year ago. However, the article's point is that you can either extend an application.cfc going down from the root, up from the subdirectory or even use mapping.