At 03:21 PM 5/26/2004, Alexander,D wrote:
Hello,
I've had a read of that first document and got the idea of multiple
repositories.
It seems to me that in this scenario it is essential to use instance
variables for the Logger rather than the class level static variables I
have been using thus fa
> From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
> Sent: 24 May 2004 18:17
> To: Log4J Users List
> Subject: Re: FW: Logging in Tomcat from classes in
> CATALINA_BASE/shared/lib
>
>
>
> It looks like this problem is a variant of the "Logging
> separation problem"
> Subject: Re: FW: Logging in Tomcat from classes in
> CATALINA_BASE/shared/lib
>
>
> Quoting "Alexander,D" <[EMAIL PROTECTED]>:
>
> > Hi,
> >
> > Hope someone can advise.
> >
> > We have an unconventional deployment of our application
Quoting "Alexander,D" <[EMAIL PROTECTED]>:
> Hi,
>
> Hope someone can advise.
>
> We have an unconventional deployment of our applications in Tomcat (4.1.x)
> where, rather than deploying classes under each webapp, they have been
> deployed together in a jar under CATALINA_BASE/shared/lib alongs
Quoting "Alexander,D" <[EMAIL PROTECTED]>:
> Hi,
>
> Hope someone can advise.
>
> We have an unconventional deployment of our applications in Tomcat (4.1.x)
> where, rather than deploying classes under each webapp, they have been
> deployed together in a jar under CATALINA_BASE/shared/lib alongs
It looks like this problem is a variant of the "Logging separation problem"
discussed at:
https://www.qos.ch/logging/sc.html
You have several options
1) use JNDIContextSelector which is natively supported in log4j 1.3 (still
in development)
2) write your own selector which fetches repositorie
Hi,
Hope someone can advise.
We have an unconventional deployment of our applications in Tomcat (4.1.x) where,
rather than deploying classes under each webapp, they have been deployed together in a
jar under CATALINA_BASE/shared/lib alongside other library jars. We do this to ease
deployment a
