I was on leave, but here's a somewhat belated +1 to your proposal.
Glyn
> If I recall correctly, JCLI didn't exist when we last had
> this discussion,
> and the impression (possibly incorrect) at the time was that Avalon's
> LogKit prereqed the Avalon Framework. In any case, JCLI not
> only doesn't
> prereq any outside framework, it has it as a part of it's design
To: [EMAIL PROTECTED]
@IBMUS cc:
Subject: RE: Interop with Log4j & AXIS
Logging in general
Richard Sitze wrote:
>
> The JCLI is an interface with thin-wrapper implementations of that
> interface for Log4J, Avalon Toolkit, J2EE 1.4 Logging API, a simple
> (System.out) logger, and a NoOp Logger. The "category" notion is handed
> straight through, so if you are using Log4J you loose only
al Message-
> From: Richard Sitze [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 08, 2002 12:00 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Interop with Log4j & AXIS Logging in general
>
>
> Given:
>
> 1. my earlier proposal to replace the direct Log4J
> depend
?
--Glen
> -Original Message-
> From: Richard Sitze [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 08, 2002 12:00 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Interop with Log4j & AXIS Logging in general
>
>
> Given:
>
> 1. my earlier proposal to repl
Given:
1. my earlier proposal to replace the direct Log4J dependency in AXIS with
the Jakarta Common Logging Interface (defaulting to Log4J),
2. The resounding silence (defaulting to a Yes vote), and
3. The current situation...
I'm moving forward as proposed. This should either correct the
