[cfaussie] Re: Include application.cfm

[Steve Onnis]

That’s correct   Tested it yesterday   All good and well to include the application.cfm file, but for the onRequestEnd.cfm to fire, you would have to create another onRequestEnd.cfm file and include the lower one within it for it to work   Steve   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Taco Fleur Sent: Wednesday, September 22, 2004 11:06 AM To: CFAussie Mailing List Subject: [cfaussie] Re: Include application.cfm   But it is not really an onRequestEnd anymore than, is it, if you just include it? I actually put the onRequestEnd in each directory as well, a bit painful sometimes, but the advantages outweigh the disadvantages.   -- Taco Fleur Senior Web Systems Engineer http://www.webassociates.com     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Elliot Russo Sent: Wednesday, 22 September 2004 10:50 AM To: CFAussie Mailing List Subject: [cfaussie] Re: Include application.cfm correct only the immediate pair are called that is why the 'extended' pair must explictly include the lower pair. I know it works cause i do it all the time   if however you create an application.cfm that includes the 'real' application.cfm and have no onrequestend.cfm the 'real' onrequestend.cfm will not fire. so sometimes all that is in the file is an include to the lower one, to maintain the pair   Elliot "Steve Onnis" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... Does that even work?   I thought the onRequestEnd.cfm file only got called after the application.cfm in the same directory   if you include it, all your doing is including a file   so if your including an application.cfm file from an application.cfm file, its not going to trigger the onRequestEnd.cfm template   No?   Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Elliot Russo Sent: Tuesday, September 21, 2004 4:46 PM To: CFAussie Mailing List Subject: [cfaussie] Re: Include application.cfm Hi Taco,   do it all the time Taco, and much as Robin described. also do it for the other little matching template onrequestend.cfm :) - remember to always make a pair.   I only ever have one cfapplication tag and that is in the root application.cfm   I only add directory (read - sub-bit of functionality) specific application.cfm when i want to append/prepend to the application processing logic provided by application.cfm/onrequestend.cfm.   I prepend when i want the 'mother' application.cfm to take action based on the input, and append when i just want to add common processing/variables.   example - a local appliccation.cfm   <cfset request.directorySecure = true> <cfinclude template="../application.cfm"><!---the next one down, which may or may not be the 'mother'--->   <cfset request.someGlobal = 35> <!--- for this scope (directory) of code---> ...   example - a local onrequestend.cfm   <cfset request.displayDebugging= true> <cfinclude template="../onrequestend.cfm">   etc   Elliot     "Taco Fleur" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... Any reason not to include application.cfm in another application.cfm?   Currently I have something like:   web/application.cfm web/object/application.cfm web/object/function/application   each application.cfm includes the one above   Just looking for some feedback I have not thought of yet ...   -- Taco Fleur Senior Web Systems Engineer http://www.webassociates.com   --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/