I'll take this on incrementally. I'll start with one package (is anything
"stable"?) to get it up and going, then I'll run as quickly (but
incrementally :-) as I can through other AXIS packages.
<ras>
*******************************************
Richard A. Sitze [EMAIL PROTECTED]
Sam
Ruby/Raleigh/IBM To: [EMAIL PROTECTED]
@IBMUS cc:
Subject: RE: Interop with Log4j & AXIS
Logging in general
02/08/2002 11:45
AM
Please respond
to axis-dev
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 the benefits
of
> using the Category methods and other utility classes that you might
> otherwise have used (certainly dynamic config).
Let me expand on this. It is an extremely thin wrapper. It has a factory
and an interface. That's it. In addition it has 5 concrete
implementations that it provides with it: Jdk14, Log4J, LogKit, NoOp, and
Simple. A total of 7 classes in all, with any 4 of the last 5 optional.
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
requirements to stay that way.
I'm +1 with Richard proceeding as planned. For everyone's sanity, I just
suggest that the changes be integrated either quickly or incrementally.
This effort is undoubtably going to touch a lot of files, and I don't want
to see a lot of changes lost due to incorrect merges.
- Sam Ruby
