Log4j 1.3.0alpha vs. Commons Logging

[Boris Unckel <bo...@gmx.net>]

Hello,

as developer engaged in an J2EE project I am always interested in Logging
Services and a heavy user of first Log4j and later Commons Logging with
Log4j.

During inspecting the new Log4j 1.3.0alpha Release I recognized a JDK
Wrapper and a new Factory Concept (org.apache.ugli**).
The idea to use a single interface which is not depending to the underlying
log implementation is very good and not new.
I am interested in the following questions:

What is the reason for not using the Commons Logging interfaces (Both for
Factories and Log)?
Is/was there an discussion to "merge" the Apache Commons Logging and Log4j
ideas/sources/goals?
Are there technical reasons to not use Commons Logging
interfaces/implementation (for example ClassLoading issues)? I am wondering
especially about creating new interfaces which do not have backward
compatibilty design goals.

I apologize my English syntax and grammar.

Boris

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

Re: Log4j 1.3.0alpha vs. Commons Logging

[Curt Arnold <ca...@apache.org>]

It is a surprisingly complex topic and contentious topic.  You might 
want to read some of the following (all linked from 
http://logging.apache.org/log4j/docs/documentation.html) for some 
background information:

http://www.qos.ch/logging/thinkAgain.jsp
http://logging.apache.org/log4j/docs/faq.html#1.9
http://www.qos.ch/logging/classloader.jsp


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