<virtual-mapping>
<resource-path>/*</resource-path>
<system-path>C:/CFusionMX/wwwroot/</system-path>
</virtual-mapping>
On other servers, I also have two direct CFMX 6.1 installs, one installed as a stand-alone server, the other installed as a stand alone server then attached using wsconfig. Neither of these other two installs have the above virtual mapping, so my guess is that it is a hold-over from CFMX 6.0. It may have been the case that mappings under CFMX 6.0 were stored in jrun-web.xml, while mappings under CFMX6.1 are now stored in neo-runtime.xml.
When this mapping is here, the following is what happens when I request a cfmx file that is under the Sun ONE Web root.
1. httpd.exe (Sun ONE) confirms that the directory exists
2. jrun.exe looks for the file a couple times in C:/CfusionMX/wwwroot, and fails
3. jrun.exe looks for the file under the Sun ONE Web root and succeeds.
Step 2 seems wasteful, since it seems to happen (fail) for every single request. Without the virtual mapping, step 2 is eliminated and everything seems to work fine. So, does anyone have any idea how/why the virtual mapping got added? Why would I want to add a virtual mapping using jrun-web.xml instead of using CFAdmin?
The default mappings in CFAdmin are usually one for the Web server root / and one for /CFIDE. Do I actually need a mapping to define the root, since I do not know of any place where I actually make use of this mapping in my code?
Thank you,
Mike Chabot
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
