Delivered-To: cgu@qos.ch
Importance: Normal
Subject: JSR47 and log4j
To: java-logging-input@eng.sun.com
Cc: cgu@qos.ch
X-Mailer: Lotus Notes Release 5.0.3  March 21, 2000
From: lee_t_hall@bankone.com
Date: Mon, 18 Jun 2001 15:20:50 -0400
X-MIMETrack: Serialize by Router on CMHSMTP1/SMTP/SVR/BANCONE(Release 5.0.7 |March 21, 2001) at
 06/18/2001 03:51:26 PM

Please hear my concern.

I have been a Sun Certified Java Programmer and Developer for four years.
Prior to that, I have been a professional C/UNIX programmer since 1983.  I
am presently serving BankOne as an IT architect in the Retail Systems
department.

I state these facts to qualify my objection to what appears to be blatant
disregard of the pragmatic Java community adoption and ad hoc
standardization on the log4j toolkit that has become a Jakarta project.
Innovation and technology evangelism should be rewarded by recognition and
endorsement - not by formal rejection by a committee (even by one which
acts with a certain amount of authority).

It seems hard to believe that anyone who has a sincere interest in adding a
logging API to the Java2 SDK could possibly ignore the org.apache.log4j
package.  Unless the JCP expert group is actually trying to cause
deliberate confusion in the community, they should simply recognize that
log4j has become the ad hoc standard and move on to endorsement.  It will
cause the community considerable inconvenience to need to "port" their code
to the result of JSR47 unless there is substantial reason to do so.
Further, it will cause even more confusion in organizations that need to
support current and older versions of the JDK.

I, for one, will continue to use and endorse the use of log4j regardless.
It is my strong professional opinion that JSR47 should be terminated with a
final report that is an acknowledgement that the community at-large has
already chosen to standardize on log4j.

Sincerely,

     Lee T Hall
     Sr Java Web Architect
     Odyssey Consulting
     614-213-2484