Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 52050 invoked from network); 22 Jun 2002 17:52:53 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 22 Jun 2002 17:52:53 -0000 Received: (qmail 2030 invoked by uid 97); 22 Jun 2002 17:53:01 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 1990 invoked by uid 97); 22 Jun 2002 17:53:00 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 1977 invoked by uid 98); 22 Jun 2002 17:52:59 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: [logging] bug: Log4J factory is more than default.. To: commons-dev X-Mailer: Lotus Notes Build V60_M13_04302002 Pre-release 2 April 30, 2002 Message-ID: From: rsitze@us.ibm.com Date: Sat, 22 Jun 2002 12:51:59 -0500 X-MIMETrack: Serialize by Router on D04NM201/04/M/IBM(Build M13TT_06062002 Pre-release 2|June 06, 2002) at 06/22/2002 13:52:48 MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=09BBE173DFF1832A8f9e8a93df938690918c09BBE173DFF1832A" Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --0__=09BBE173DFF1832A8f9e8a93df938690918c09BBE173DFF1832A Content-type: text/plain; charset=US-ASCII 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? ******************************************* Richard A. Sitze rsitze@us.ibm.com CORBA Interoperability & WebServices IBM WebSphere Development --0__=09BBE173DFF1832A8f9e8a93df938690918c09BBE173DFF1832A--