On Thu, 02 Aug 2001 08:56:55 Jeremias Maerki wrote:
> > Isn't logging going to be a standard part of JDK 1.4? I thought that
> was 
> > going to be based on IBM's Log4J. Is Avalon's logging based on that? If
> > not, should the 'standard' be considered? IIRC JDK 1.4 logging includes
> > the ability to log to syslog (on unix) and whatever the logging 
> > mechanism is on Windows.
> > 
> > Just curious.
> If you look at the Avalon dev mailing list archives you will find a
> heated discussion about JDK 1.4 logging, LogKit and Log4J. I think the
> common opinion there is something like: JDK 1.4 logging is not good
> enough. I know this is simplified, but you can read the details yourself.
> :-) And anyway, JDK 1.4 is not available, yet, so we will probably use
> what's available.
> Avalon uses LogKit and LogKit is part of the Avalon project. When using
> Avalon LogKit's the first choice. There was a discussion at Avalon if a
> common lightweight API should be defined that could be backed by LogKit
> Log4J and JDK logging. But so far nobody has takes this idea forward,
> yet.
> Both Log4J and LogKit can be easily extended (or are already able) to
> log to syslog and Windows EventLog.

JDK1.4 is not really likely to be useful (we are still in jdk1.1, etc.).

So between logkit and log4j I think logkit is the better option simply
because cocoon uses it. (that's the only thing that tips the balance, I'd
rather just choose than not go anywhere.)

They both essentially do the same thing and as long as we keep the
dependance minimal (shouldn't be too hard) then we will be making a step

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to