logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: conversion patterns and caller class information
Date Sun, 06 Jun 2004 09:59:26 GMT

Hi Jake,

At 08:16 PM 6/5/2004, Jacob Kjome wrote:

>I'm noticing an issue with using the conversion characters which generate 
>caller class information.  In a project I'm working on, logging is done 
>via a sort of Monitor framework.  Anything can back the Monitor whether it 
>be System.out, nothing, Log4j, etc.  This makes it so that no logging 
>framework becomes a runtime dependency of the library unless a user 
>explicitly configures the library to use a particular Monitor 
>implementation such as one backed by Log4j.  The thing is, classes call 
>the monitor to let the obfuscated logger implementation do the 
>logging.  As such, if I use the Log4j implementation and use the 
>conversion characters such as "C", "F", "L", and "M", it ends up looking 
>like logging came from the Log4jMonitor rather than the class that is 
>calling the log4j monitor, which is what I'd want.

With respect to the conversion characters such as "C", "F", "L", and "M", 
how is monitoring different than wrapping? You are aware of the





method right?
>The whole Monitor idea kind of came from this post:

How is the monitor handed down to the reusable component? It looks to me 
like the logger initialization problem has been replaced by the monitor 
initialization problem. I don't see the gain... Anyone care to explain?


Ceki Gülcü

      For log4j documentation consider "The complete log4j manual"
      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp  

To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

View raw message