"{WEBROOT}/.app" --> "/mysite"
Then, in my webroot, which has a mapping of "/", I create a new Application.cfc file that extends "mysite.Application". In fact, I place all or most of the functionality of {WEBROOT}/Application.cfc inside "mysite.Application" and the subclass simply looks like this inside:
<cfcomponent extends="mysite.Application" output="false">
</cfcomponent>
</cfcomponent>
On Apr 12, 2005 1:31 PM, Daniel Short <[EMAIL PROTECTED]> wrote:
I played just a little more, and the only way I can get it to work is to set
the name, sessionmanagement and sessiontimeout in the
/members/application.cfc as well... This means that any App.cfc that extends
the parent (in my case, /siteroot.cfc, which extends /App.cfc) has to have
the same <cfapplication> variables as the root App.cfc in order to work
correctly.
This seems like a design flaw that should definitely be worked out of CFMX7.
Dan
> > I guess you'd have the same problem any time you wanted to
> > extend a CFC of
> > the same name that is in the root. I can't think of a way
> > around that aside
> > from using a root mapping.
----------------------------------------------------------
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]
--
Paul Kenney
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.pjk.us ----------------------------------------------------------
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]
