Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 23551 invoked from network); 3 Sep 2003 21:16:11 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 3 Sep 2003 21:16:11 -0000 Received: (qmail 24625 invoked by uid 50); 3 Sep 2003 21:19:03 -0000 Date: 3 Sep 2003 21:19:03 -0000 Message-ID: <20030903211903.24624.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 22770] - Logger element within Context element in Context.xml file not getting recognized by Tomcat X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22770 Logger element within Context element in Context.xml file not getting recognized by Tomcat medthomas@ntlworld.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From medthomas@ntlworld.com 2003-09-03 21:19 ------- I have tested this successfully with the TC4-HEAD. The relevant code hasn't changed since 4.1.24 so this should also work for you. If you want to deploy a web application outside the standard webapps directory with its own context.xml then one way is as follows. (I have shown the filepaths etc as per my setup. You will need to change these to match your environment) 1. Open the manager web app. 2. Scroll down to the install section. 3. In the "Install directory or WAR file located on server" section complete the following boxes: XML Configuration file URL: file:C:/javadev/bug22770/WEB-INF/context.xml WAR or Directory URL: file:C:/javadev/bug22770 4. Click install. The content of my context.xml was: I am therefore resolving this bug as WORKSFORME.