Hi Jason, I have also noticed a similar thing when using instance manager from within CF7 admin. I am much more comfortable using the Jrun4 Admin and creating my new CF instances that way and then deploying them as an extracted ear/war under the jrun4/servers directory. I have a jrun-web.xml under each of my server instances now and it all behaves as it should. At least this way i jave full control over what the J2EE server is doing, rather than the cut down wizard style used by the CFadmin..
hth Phil ------------------------------------- Phil Rasmussen Tourism Queensland (eCom) e: [EMAIL PROTECTED] w: www.qhx.com.au (Queensland Holiday Xperts) "Chris Velevitch" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] In my case I'm on Windows, so I have:- c:\bin\mx\JRun4\servers\cfmx7\SERVER-INF\temp\cfusion.war91030902\WEB-INF\jrun-web.xml but I also have:- c:\bin\mx\JRun4\servers\cfmx7\cfusion.ear\cfusion.war\WEB-INF\jrun-web.xml as well as:- c:\bin\mx\JRun4\servers\cfmx7\default.ear\cfusion.war\WEB-INF\jrun-web.xml The first one is my actual server instance. It has something to do with some auto-deployment feature of JRun. So, which jrun-web.xml are changing? --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
