Dear Graham
Thanks for your response. I understand that if other parts of JKD 1.4 is
using the logging api it will be difficult to make changes. However
it
is not clear to me that the JSR-047 has recieved the same attention as
for instance the Java collection framework did, where the Java community
recieved beta implementations and the FAQ list gave very good reasons
for
the design and its deviations from existing collection libraries.
Regards
Henrik
-----Original Message-----
Sent: Thursday, June 14, 2001 1:18 AM
To: henrik.fredholm@telenor.com
Subject: Re: Please adopt log4j as the logging API shiped with JDK
1.4
Henrik,
Thanks for your interest in the logging APIs.
As Ceki noted, IBM has been a very active participant in the
JSR-047 logging JSR. When the logging JSR was initiated in
January 2000, IBM had both the log4j work at IBM research and
the JLog work at IBM Tivoli. The Tivoli work built on IBM's
earlier product logging experience and included features like
internationalization that were then not present in log4j.
IBM's involvement in JSR-047 was focused on their JLog
experience which had seen a lot of use in IBM products.
However, Ceki also provided useful input from log4j, and that
has influenced some parts of the logging APIs.
In designing the APIs we've tried to draw from numerous
sources and we've tried to support a wide set of requirements.
It's inevitable that when there is a new standardization
effort it will make some different choices from some of
the existing APIs. We went through a similar experience
with JDBC. It built on a bunch of earlier work, but it
wasn't exactly like any of them. Unfortunately we delayed
adding a JDK logging API for too long, and I think it
is important that we resolve that in Merlin.
Unfortunately we are quite late in the Merlin cycle and
we can't really accommodate major API changes at this point.
However, I will be studying Ceki's comments carefully.
thanks
-
Graham
henrik.fredholm@telenor.com wrote:
>
> Hi,
>
> Could you please adopt log4j as the logging API shiped with JDK 1.4.
This
is
> an excelent API that I feel is superior to JSR47 and addresses the
needs
we
> have for loging. It even works with existing JDKs. We have adopted it
as
> standard for all J2EE BEA WebLogic based projects in our
organization.
>
> Thanks
> Henrik Fredholm
> J2EE Coordinator/Architect for
> Telenor Mobil