tracker issue : CF-3039343

Problem:

Application-specific mappings do NOT take priority over server-level (global) mappings, which brings them within a nanometer of being absolutely useless.Without application-level mappings, it is difficult to run multiple versions of frameworks (for example, an old application in Model-Glue 2 and a new application in Model-Glue 3) on the same server, and take advantage of mappings. In order to do this, you must remove the global mapping and either include the framework in the web root (which can cause a significant amount of duplication and maintenance headaches, and is not always an option, for example: when the application lives in a sub-folder) or use a per-application mapping.Ideally, I would like to see per-application mappings take precedence over global mappings. That is how it *should* work. I hope you don't decline to fix this bug citing "backwards compatability" because the current functionality is just *broken*.
Method:

create a folder "a" with foo.cfm, contents: "foobar-global"create a folder "b" with foo.cfm, contents: "foobar-local"create a global mapping "foo" in CF Admin that points to the folder "a"create an application with a per-app mapping to the "b" folderin your application, do: <cfinclude template="/foo/foo.cfm" />you will see the message "foobar-global", instead of the expected result "foobar-local" from your per-app mapping.
Result:

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

Watson Bug ID:	3039343

External Customer Info:
External Company:  
External Customer Name: Adam Tuttle
External Customer Email: 71DA001D4586B5B5992015D5
External Test Config: 07/17/2009

Attachments:

Comments: