Delivered-To: cgu@qos.ch
From: "Edwards, Del" <Del.Edwards@mirant.com>
To: "'java-logging-input@eng.sun.com'" <java-logging-input@eng.sun.com>
Cc: "'cgu@qos.ch'" <cgu@qos.ch>
Subject: Log4j
Date: Wed, 13 Jun 2001 16:49:32 -0400
X-Mailer: Internet Mail Service (5.5.2652.33)
X-FREE-OF-KNOWN-WORMS: Scanned by Mirant.Com for known email worms
X-Filtered-By: [Mirant] Powered by PerlMx v1.1, free for personal or educational use; visit http://www.ActiveState.com/Products/PerlMx/info for more info

    After using Log4j a few months ago, I was "surprised" that to see that
JSR47 was a request to "duplicate" functionality that already existed in
Log4j. After reading the recent comparison of the two  logging APIs ( at "
http://jakarta.apache.org/log4j/docs/critique.html
<http://jakarta.apache.org/log4j/docs/critique.html> " ) I must say it seems
"silly" not to adopt Log4j as the logging API that ships with jkd1.4 (as
well as with existing compatible jdks !).
    I think its great seeing the JSR process in action. I think it does
wonders for the language. It would be disappointing, however, to see such a
useless waste of time as JSR47's re-implementation of an existing logging
API - that will result in an "official" API that is untested,
yet-to-be-accepted, has less functionality and is harder to use.
 
Thank you,
 
Del Edwards
Java Developer