Delivered-To: cgu@qos.ch
X-Sender: d6y/mail.btinternet.com@pop3.norton.antivirus
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Thu, 14 Jun 2001 14:11:44 +0100
To: java-logging-input@eng.sun.com
From: Richard Dallaway <richard@dallaway.com>
Subject: community process
Cc: cgu@qos.ch, pmo@jcp.org

I think it's great that logging has been recognized as being important enough to include in the JDK.

I have no strong technical views telling me if JSR47 is preferable to log4j, although from a casual glance log4j looks both more mature and more feature rich.

My concern is perhaps more general in the way that the JCP is working (or not working) with established projects.  The three projects that come to mind are:
1.  log4j v. JSR47
2.  Apache struts v. JavaServer Faces
3.  Apache Xalan/Xerces v. JAX.

There may be very good reasons why Sun is spending effort on building projects that already have tried and tested counterparts.  Maybe there are things missing from other projects, maybe Sun can do a better job, maybe it's a licensing thing, maybe the project code quality isn't high enough.  I don't know, but it would be refreshing to get a statement giving a clear indication.

The big worry is that there's some fundamental issue with the community process that's preventing collaboration.  I'd appreciate some clarification on this.

Regards
Richard