logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject RE: JDJ - log4j vs java.util.logging
Date Thu, 24 Mar 2005 17:29:24 GMT
At 04:01 PM 3/24/2005, Boris Unckel wrote:

>I think it is more interesting to open existing solutions (aka backends) for
>other frontends and to improve the way to lookup/bind/manage the backend.
>(See also threads discussing classloader issues and dynamic/static


>In my opinion there should be no overwhelming frontend for every case of use
>(See also thread discussing "Enterprise Logger") (In German "Eierlegende
>Wollmilchsau" - "all-in-one device suitable for every purpose").
>But there should be one interface for each case of use (i.E. Simple (like
>JCL Log, ugli ULogger), I18N (parts of JSR47), extend (parts of JSR47 with
>log(String sourceClass, String sourceMethod,...)


>A new project binds people to administrative tasks, will confuse developers,
>split communities. As I learned in the last month, there is very much know
>how existing in JCL and log4j. I would wonder if the mentioned technical
>problems are not solvable in the current projects (may cause incompatibility
>with former releases).

True. Backward compatibility is a not small problem.

>One idea could be to split log4j- (loggers, appenders, and layouts) -loggers
>into two parts, one for doing (backend) and one for accessing (frontend),
>the component for accessing then can be used by wrappers or extended with
>special (existing?) interfaces.

Yes, this has been partially accomplished by UGLI log4j split, although as 
you suggest, there is still more work to do.


Ceki Gülcü

   The complete log4j manual: http://www.qos.ch/log4j/

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

View raw message