What about creating an Application.cfc that extends the root Application.cfc
Your root Application.cfc: <cfcomponent /> Your Application.cfc in /subdir1/ <cfcomponent extends="Application" /> Your Application.cfc in /subdir1/subdir2/ <cfcomponent extends="subdir1.Application" /> Somewhat like <cfinclude template="../Application.cfm"> Your subfolders could override events like onRequestStart & End, perhaps calling super methods, and leave session and application events in the base class. Sounds good... haven't tried it... not a clue if it would work. Anybody? -nathan strutz http://www.dopefly.com/ On Sat, 5 Mar 2005 16:13:38 +0100, Nando <[EMAIL PROTECTED]> wrote: > I hear you John. At this point, i'm not even sure how to refer to the > instance that Application.cfc creates. I dug up the post i've been referring > to: > > ****** > > "This is actually exactly what we do (and many others), and unfortunately, > you're not going to find a solution for what you're looking for without > resorting to cfmappings. In our case, since we can't use mappings (or > rather, refuse to), that means we can't use inheritance in many situations. > This, unfortunately, includes all of the neat inheritance things you can do > with Application.cfc > > Roland" > > ****** > > I was thinking i must have missed something that everyone else knew about by > now (wouldn't be the first time!). > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
