Delivered-To: cgu@qos.ch
Date: Tue, 19 Jun 2001 14:00:30 +1000
From: Brett Morgan <brett@pulse.itd.uts.edu.au>
To: java-logging-input@eng.sun.com
Cc: cgu@qos.ch
Subject: Request to use log4j as basis of official logging API in jdk1.4
X-Mailer: Mutt 0.95.1i
X-Operating-System: SunOS pulse 5.6 sun4u sparc

I am happily awaiting jdk1.4's release for many reasons. Finally being
able to use the equivalent of mmap and poll excite me. The new work in
Swing is looking very promising.

But, honestly, I am worried about the direction logging is taking.

Having used log4j in several large websites,
(http://www.tradingroom.com.au being a prime example), I love
log4j. It works for my group of coders very well.

I was looking forward to the adoption of a standard logging standard,
but various problems with it make me less willing to use the standard,
and stay with the tried and true solution.

For example, having runtime behavior dependant on  configuration
ordering, scares the crap out of me. I know most of our junior coders
believe, on a metaphysical level, that configuration files can be cut
and pasted to their hearts content. If this cut'n'paste
methodology introduces subtle bugs, then I will never see the end of the
wasted debugging effort.

The multitude of logging levels looks, honestly, like something
designed by an academic or a committee. When was the last time these
guys actually stepped out and coded something? Something large?
Something with a team of 20 coders? Something with a fair percentage
of recent uni graduates involved?

Log4j is a well respected, widely used, and robust, logging API. The
industry is already using it.

Adopt it. Please don't divide the community.

brett

--
email: Brett.Morgan@uts.edu.au
phone: 0416-241-898

"Just because I'm not a real person doesn't mean I'm not a *good* person."
  "That's... that's beautiful, Fuzz.  You want to host a telethon?"
                -- A Disney construct who can resemble anyone revels
                   in his crimes in SONIC DISRUPTORS