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: Wildcards in log configuration
Date Thu, 15 May 2003 16:19:25 GMT

The reason was speed. It's pretty hard to get multi-d  capability right.
It will probably be a patented feature of log4j 1.3.

At 05:13 PM 5/15/2003 +0100, you wrote:
>Any idea why it was throw away? Was it (and is it still) considered
>overengineering?
>
>Brendan.
>
>-----Original Message-----
>From: Ceki Gulcu [mailto:ceki@qos.ch]
>Sent: 15 May 2003 17:10
>To: Log4J Users List
>Subject: Re: Wildcards in log configuration
>
>
>
>Fascinating question. Log4j as it exists today does not support wildcards.
>Interestingly enough, the first version of log4j which was never published
>had multi-dimensional capability. That was in 1996!
>
>At 04:54 PM 5/15/2003 +0100, you wrote:
> >Hi,
> >    I have found in my own use of log4j, the naming of my loggers tends to
>be
> >more complex than a simple hierarchy - more like a multi-D array:
> >
> >For example in a component based system that uses the ModelViewController
> >design pattern in each component, I name the logger of a given class based
> >on the component AND pattern role e.g. calendar.view or task.model.
> >
> >The choice of which order I name them is very important. I can name them so
> >that either I can switch the levels of all components together or all
> >pattern roles together. But not both. I imagine that other uses out there
> >use similar naming techniques, with even higher numbers of dimensions.
> >
> >Is it possible that wildcards could be used in the identification of
> >loggers?
> >
> >e.g. <logger name="app.*.model ">
> >          <level value="debug\>
> >         <\logger>
> >
> >I realise that this might create a situation where more than one logger
> >might seem to refer to the same thing - but the existing approach of
> >accepting the more specific one would resolve this.
> >
> >Maybe something like this already exists and I have just wasted some
> >bandwidth - in which case sorry about that!
> >
> >Regards,
> >Brendan.
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
>--
>Ceki  For log4j documentation consider "The complete log4j manual"
>        http://www.qos.ch/shop/products/clm_t.jsp
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-user-help@jakarta.apache.org

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


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


Mime
View raw message