Hello All!
This post relates to Jen N's on Extending Application.cfc.
We have multiple environments set up on both Windows and Unix, with Unix being
our production. Since moving to Unix, we replaced the so convenient
CGI.REMOTE_USER with a process that calls web services, stored procedures and
overall, not nearly as nice to use. As it is, what we are working on is two
parts. First the application shell which handles all items common to part 2,
the sub applications. The application shell is also the piece that will handle
the time out for any application that is open below it, with the possibility of
up to 4 open at the same time, in different frames. The catch here is the
application container does not sit on the wwwroot for all the environments, and
it may even sit at different levels of the development environment. I need to
mention that as I had seen reference to creating a proxyApplication.cfc. From
my research, it appears that will only work if the application folder resides
on wwwroot,and in testing, seems definitely to be the case.
One environment may look like this
wwwroot
-ContainerApplication Folder
-Application.cfc (for ContainerApplication)
-ApplicationGroup1 Folder
-DataApplicaton1 Folder
-Application.cfc (for DataApplication1)
-ApplicationGroup2 Folder
-CatalogApp1 Folder
-Application.cfc (for CatalogApp1)
-ApplicationGroup3 Folder
-SalesApp1 Folder
-Application.cfc (for SalesApp1)
-ApplicationGroup4 Folder
-MaintenanceApp1 Folder
-Application.cfc (for MaintenanceApp1)
It wouldn't be to bad for this as the subApps App.cfc could use
extends="ContainerApplication.Application" and then <cfset
super.onRequestStart()>
That makes the code non portable to our other various environments then. For
example, one dev instance maybe like this...
wwwroot
-ValidationFolder
-Application1Validation
-ContainerApplication Folder
-Application.cfc (for ContainerApplication)
-ApplicationGroup1 Folder
-DataApplicaton1 Folder
-Application.cfc (for DataApplication1)
-ApplicationGroup2 Folder
-CatalogApp1 Folder
-Application.cfc (for CatalogApp1)
-ApplicationGroup3 Folder
-SalesApp1 Folder
-Application.cfc (for SalesApp1)
-ApplicationGroup4 Folder
-MaintenanceApp1 Folder
-Application.cfc (for MaintenanceApp1)
>From what I have been reading, some people posted in relation to this on
>shared hosting, not knowing necessarily where their root app will reside.
>Each sub Application.cfc has thing relating to its app from data source names,
>environment tracking, pathing which I have not come up with an easy way of
>putting into the single Application.cfc at the root. I believe we have in the
>neighbor hood of 25 applications spread throughout the 4 application group
>folders, some being down more levels that what is shown above. This is where
>it would be nice to be able to use a variable name in the extends statement,
>extends="#fromCGIPATHSomething#.Application" and then still be able to use the
>super.
Any Suggestions?
Thanx!!!
Bill
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion MX7 and Flex 2
Build sales & marketing dashboard RIAâs for your business. Upgrade now
http://www.adobe.com/products/coldfusion/flex2?sdid=RVJT
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274244
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
