t: RE: [commons-logging] JCL with log4j on WebSphere 6
Hi Seamus,
The reason the priority approach isn't mentioned in wiki docs etc is
that the priority config option was only added in the most recent
release. It's great that it happens to solve this problem for you, and
in fact it was int
is Unckel [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 26, 2006 3:56 PM
> To: Jakarta Commons Users List
> Subject: Re: [commons-logging] JCL with log4j on WebSphere 6
>
>
> Hello Seamus,
>
> ---- Original-Nachricht ----
> Datum: Tue, 26 Sep 2006 10:30:4
lass other than LogFactoryImpl or else use the
deprecated Log4jFactory (which doesn't sound appealing).
Regards,
Seamus
-Original Message-
From: Boris Unckel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 26, 2006 3:56 PM
To: Jakarta Commons Users List
Subject: Re: [commons-logging]
Hello Seamus,
Original-Nachricht
Datum: Tue, 26 Sep 2006 10:30:43 -0400
Von: "Kerrigan, Seamus" <[EMAIL PROTECTED]>
An: commons-user@jakarta.apache.org
Betreff: [commons-logging] JCL with log4j on WebSphere 6
> Hi,
>
> I am trying to use JCL 1.1 wit
Hi,
I am trying to use JCL 1.1 with log4j in an application which is
deployed on WebSphere 6.0.2. I found that the documentation for running
JCL on WebSphere, only works on WebSphere 5 and not 6.
In WebSphere 5, the container has it's own custom implementation of
LogFactory. The documented way fo
