Delivered-To: cgu@qos.ch
Date: Thu, 14 Jun 2001 16:39:49 -0600
From: Doug Erickson <doug.erickson@part.net>
X-Mailer: Mozilla 4.74 [en] (WinNT; U)
X-Accept-Language: en
To: java-logging-input@eng.sun.com
Subject: log4j

Hi JSR47 Folks --

One of the main things I've been looking forward to in the release of
JDK 1.4 is the logging API.  I'm familiar with log4j, which has filled a
big void in our development.  At first glance, it seems that the
"standard" logging API uses the same concepts.  On closer inspection
though, several drawbacks are revealed.  The log4j guys, as I'm sure
you're aware, do a good job of describing these gaps
(http://jakarta.apache.org/log4j/docs/critique.html).

To me, it seems like the main problems could be avoided by linking child
to parent as log4j does.  Isn't this an implementation detail?  Why
can't it be changed? 

I realize now that 1.4 beta is out the door, all this is probably moot.
Consider this, however:  you know you need to get the logging API out
there, right?  Because it's long overdue... Well, it's ALREADY
_too_late_!  People didn't sit around waiting for the JCP to do its
thing -- we had software to write!  So by ignoring that established base
of log4j users, I think you're risking the perceived integrity of the
JCP.  It'd be better to spend the next six months finding more common
ground with this significant group of log4j users.

Thanks for your consideration,

Doug Erickson