commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rsi...@us.ibm.com
Subject [logging] bug: Log4J factory is more than default..
Date Sat, 22 Jun 2002 17:51:59 GMT
Bugzilla appears to be down...  so before I forget:

Current LogFactoryImpl logic forces use of Log4j if it's in the classpath
(constructor sets proxyFactory to Log4jFactory).  This is not critical,
because the factory CAN be overridden.  If Log4j is not in the classpath,
then we fall back to looking for different implementations of Log
(including log4j.. way down in the list as it was intended).

At issue, I believe, is how to properly initialize Log4j if it IS the
default, so it may be that the "most" correct behaviour is to leave the
proxyfactory as null UNTIL we default to Log4j, then have that logic set
the proxyFactory to ensure that Log4j is properly initialized.

Any comments before I make such a change?

<ras>


*******************************************
Richard A. Sitze            rsitze@us.ibm.com
CORBA Interoperability & WebServices
IBM WebSphere Development
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message