tracker issue : CF-3041319

Problem:

Application mapping to a *.zip\*.jar file

We are currently heavily using Application level mappings. It is a huge deal for us. This allows us to have many version of our application or installation in the same web server space without having to worry about CF accidently searching for CFCs in the wrong place.It is our opinion that even looking at the webroot while doing CFC resolution is a problem with CF not a feature.CF is evolving towards OOP and like Java really needs the "classpath" idea. App mapping gives us this with fairly good success.We are also working towards having virtually no files in our wwwroot directory for security. We can place these cod files somewhere safter.

Currently application mappings can point at physical directories. We are placing our libraries like ColdBox, etc in places like c:\code\coldbox and then have an application mapping point there for the "coldbox" namespace.It would be nice if we could just point at a .JAR file instead of having to copy all the files around.Our main application directory usually only has a application.cfc and an index.cfm for the web server to hit. We are even moving towards renaming index.cfm to i.c and/or using a web server mapping to make the URL look like http://server/app/ vs. 
http://server/app/index.cfm .

The idea is we are trying to "install" our CF app and then creating an application.cfc that configures it. By setting the DSN, etc. etc. We often use a cfinclude in application.cfc to isolate these things.By allowing us to use application mappings as JARs we should be able to have our entire application be a just a few simple files that we can plop in a directory...and then setup our application mappings to those files. Imagine if CFIDE becomes just a .JAR file...even the installation of the server would be faster and easier to move reference to CFIDE around.
Method:


Result:

Application mapping to a *.zip\*.jar fileWe are currently heavily using Application level mappings. It is a huge deal for us. This allows us to have many version of our application or installation in the same web server space without having to worry about CF accidently searching for CFCs in the wrong place.It is our opinion that even looking at the webroot while doing CFC resolution is a problem with CF not a feature.CF is evolving towards OOP and like Java really needs the "classpath" idea. App mapping gives us this with fairly good success.We are also working towards having virtually no files in our wwwroot directory for security. We can place these cod files somewhere safter.Currently application mappings can point at physical directories. We are placing our libraries like ColdBox, etc in places like c:\code\coldbox and then have an application mapping point there for the "coldbox" namespace.It would be nice if we could just point at a .JAR file instead of having to copy all the files around.Our main application directory usually only has a application.cfc and an index.cfm for the web server to hit. We are even moving towards renaming index.cfm to i.c and/or using a web server mapping to make the URL look like http://server/app/ vs. http://server/app/index.cfm .The idea is we are trying to "install" our CF app and then creating an application.cfc that configures it. By setting the DSN, etc. etc. We often use a cfinclude in application.cfc to isolate these things.By allowing us to use application mappings as JARs we should be able to have our entire application be a just a few simple files that we can plop in a directory...and then setup our application mappings to those files.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3041319

External Customer Info:
External Company:  
External Customer Name: Eric Twilegar
External Customer Email: 3D9A02F5446CCE0A992015D5
External Test Config: 04/13/2010

Attachments:

Comments: