mappings dont have to be cf-mappings it will just as happily use the webroot. so if you need to change the mapping per site
ie. staging and production environments then just assume all your codebase is sitting off the webroot.
trade off = you need to put any CFC's and taglibs you need underneath your wwwroot for each site
Chris, nice idea about the application.cfc - if that works COOL! but i think you need it defined on every template from memory :( this may have changed for CF7.
I just stick with the slighlty more ugly CFMODULE as you can pass a dynamic template name as an agument.
Pat
On 7/4/06, Chris Velevitch
<[EMAIL PROTECTED]> wrote:
> (Slightly) longer answer: <cfimport> is interpreted at 'compile time' ie.
> when the CFML is converted to Java classes, so any CF variables like
> Application/Request/Session aren't available to it.
That makes sense if it's done at compile time.
How about if I were to create an Applicaiton.cfc and define an
onRequest function and do a cfimport before I cfincluded
#Arguments.Targetpage#? This would allow me to make the taglib global
to every cfm page, that way I'd have only one place to change.
How does Application.cfc work with cfc's?
Chris
--
Chris Velevitch
Manager - Sydney Flash Platform Developers Group
www.flashdev.org.au
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cfaussie" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~----------~----~----~----~------~----~------~--~---
