Re: Re: Questions about Code.debug(), Log.event()

The current Jetty log mechanism is a facade logging mechanism like.
you can direct logs to zero or more LogSinks that can handle the logs
in anyway that you like.

Jetty already has LogSinks for files, JBoss logging (log4J) and
java 1.4 logging.

I don't propose changing the Jetty log instrumentation (the log
code in the classes), only perhaps creating a standard log4J
logSink.

cheers


Scott Eade wrote:> The Jakarta commons-logging 
(http://jakarta.apache.org/commons/logging.html)
> and Avalon logging (http://jakarta.apache.org/avalon/logkit/index.html)
> subprojects provide solutions that act as an intermediate logging layer that
> allows different logging mechanism to be plugged into applications (e.g.
> log4j, jdk1.4 logging, etc.)
> 
> Using one of the above mechanisms allows you more flexibility than just
> going with log4j.
> 
> Debate rages over at Jakarta as to which is the better solution, ultimately
> they may well merge.
> 
> Cheers,
> 
> Scott



-- 
Greg Wilkins<gregw@xxxxxxxxxxx>             Phone/fax: +44 7092063462
Mort Bay Consulting Australia and UK.          http://www.mortbay.com


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/CBxunD/vN2EAA/xGHJAA/CefplB/TM
---------------------------------------------------------------------~->

For the latest information about Jetty, please see http://jetty.mortbay.org

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/