tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22770] - Logger element within Context element in Context.xml file not getting recognized by Tomcat
Date Wed, 03 Sep 2003 21:19:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22770>.
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:
<Context cachingAllowed="true" path="/bug22770" docBase="C:\javadev\bug22770" >
 <Logger className="org.apache.catalina.logger.FileLogger"
 	directory="logs" 
 	debug="0"
 	prefix="localhost_bug22770_log." 
 	suffix=".txt" 
 	timestamp="true" 
 	verbosity="4"/>
</Context>

I am therefore resolving this bug as WORKSFORME.

Mime
View raw message