That seems to be a characteristic of the way Log4J is designed -- if you
want to share the classes, you also need to share the configuration
properties. There's nothing Tomcat can do about where Log4J tries to load
its properties from.
Note that global sharing seems to be Log4J's design intent -- you would
use a separate Category (or set of Categories) for each web app, and be
able to tune the configuration all in one place.
Craig
On Tue, 18 Sep 2001, Jiger Java wrote:
> Date: Tue, 18 Sep 2001 12:21:15 +0530
> From: Jiger Java <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: Tomcat 4 and Log4J
>
> Hi Craig,
> Things are working now. What I did was to put log4j.properties in
> WEB-INF/classes & log4j.jar in WEB-INF/lib. But as u will agree this is not
> optimum since I will then have to put log4j.jar in all WEbapps. So I moved
> log4j.jar into common/lib then problems start. If I put log4j.jar in
> $CATALINA_HOME/lib & log4j.properties in $CATALINA_HOME/classes then also it
> works but then now my log4j.properties is shared across all webapps & I cant
> have individual .properties files. Any idea how I can have one log4j.jar but
> individual log4j.properties per webapp. No putting log4j.jar in common/lib &
> .properties in WEB-INF/classes does not work.
>
> Awating ur reply,
> Thanks,
> Jiger
>
>
> >From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: <[EMAIL PROTECTED]>
> >Subject: Re: Tomcat 4 and Log4J
> >Date: Mon, 17
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>
