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

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
-- 
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
.Mac Chat/AIM: seade at mac dot com

> From: "Evan Koffler <evanlist1@xxxxxxxxxxxxxx>" <evanlist1@xxxxxxxxxxxxxx>
> Reply-To: jetty-support@xxxxxxxxxxxxxxx
> Date: Fri, 13 Dec 2002 15:04:29 -0000
> To: jetty-support@xxxxxxxxxxxxxxx
> Subject: [jetty-support] Re: Questions about Code.debug(), Log.event()
> 
> Greg,
> 
> The primary maintainer of log4j has a document describing how to use a
> feature of Log4J that can support different loggers for multiple
> webapps within a servlet container. Pulling from the intro of the
> document it says:
> 
> ====== quote =================
> The problem: Logging Separation
> 
> Since time immemorial users have struggled to control the logging
> configuration of multiple web-applications deployed on the same
> Servlet Container (e.g. Tomcat). If you think that in your environment
> you will always run one and only one web-application, then do yourself
> a favor, stop reading. This technical document is likely to be waste
> of your time.
> 
> What does separation of logging mean? In a separated logging
> environment, each web-application can configure log4j in different
> ways such that the settings of one web-application do not interfere
> with the settings of another. A variant of this problem is the
> separation of web-application logging and the logging of the container
> itself. 
> ====== quote =================
> 
> The full document can be found at:
> http://qos.ch/logging/sc.html
> 
> Given this, I think log4j would be beneficial (and fit the rest of my
> app using it).
> 
> Just a satisified user helping out how I can,
> Evan
> 
> 
> 
> 
> --- In jetty-support@xxxxxxxxxxxxxxx, Greg Wilkins <gregw@xxxx> wrote:
>> 
>> The simplest thing to do if you want different logging setup
>> is to instantiate each jetty in it's own classloader - that way
>> the statics are not shared.
>> 
>> I have considered moving to log4j - but that would not help
>> you here either.
>> 
>> cheers
>> 
> 
> 
> 
> 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/
> 
> 


------------------------ 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/