We have a Coldfusion server that hosts several applications, all in its own subfolder. Sort of:
- / webrootfolder / applicationA
- / webrootfolder / applicationB
In addition, on the development server, we have a copy of this application for each developer, each of which is a working copy of Subversion:
- / webrootfolder / applicationA_dev1
- / webrootfolder / applicationA_dev2
- / webrootfolder / applicationA_dev3
Since we are starting Coldfusion 7 (with serious resistance to upgrades), I found that I want to use CFCs in packages. Here are the various problems, attempts to solve and problems with them:
- Using the relative name of the component only works if there is one package that can create a mess in one folder.
- Using subpackages works as long as you never reference components in the parent packages, which seems to happen easily when extending, initializing, or using the component as the cfargument type.
- Using the full CFC path, starting from the root, does not work with our multiple copies for each developer. ** Using a dynamic path with a variable was my solution at the moment ... until I realized that it does not work with extends or cfargument type ... ** Using server mappings does not work in development, as we will have one alias for one copy of the developer. I expect the code to be folder independent. ** Using application-specific mappings (defined in Application.cfc) does not work because CF7, not CF8 +.
- ( "../../" ) . , , .
** , . Coldfusion , , -, .
- Coldfusion -,
/webrootfolder/applicationA ( ).
** , . , , .
** ( , , ), , .
- / -
, , -/ IIS 6. , , , Unix/Apache. -. , , "domain.com/appA" "/webrootfolder/applicationA". - IIS . Coldfusion ( CFC ), , - (/webrootfolder).
IIS , 8080 ( 80 ). /webrootfolder/applicationA/cfm ( ). Coldfusion "" CFC /webrootfolder/applicationA/cfm/Object.cfc.
, , . , , , . : ? ( ). , , HTTPS ( ). , , , .
...
- ? "" ?
Coldfusion , , IIS, , , , URL- .