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 20171] - weird: log4j and filter initialization
Date Fri, 23 May 2003 07:50:11 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=20171>.
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=20171

weird: log4j and filter initialization

remm@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From remm@apache.org  2003-05-23 07:50 -------
I'll have to ask for a test case here to investigate further.

Deploying a webapp outside the Host appBase doesn't (shoudln't) make a
difference, and doesn't require allowLinking to work fine. You only need that
flag if your webapp needs to access items which are symlinked to outside its
directory.

JARs which are put in server/lib are not visible to web applications (except
privileged webapps, which get to "see" the container classes). You need to put
them in common/lib or shared/lib.

One last note: Tomcat 5.0.2 is an alpha release.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message