Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 51851 invoked from network); 6 Jun 2002 08:18:08 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 Jun 2002 08:18:08 -0000 Received: (qmail 3057 invoked by uid 97); 6 Jun 2002 08:18:13 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 3004 invoked by uid 97); 6 Jun 2002 08:18:13 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 2992 invoked by uid 98); 6 Jun 2002 08:18:12 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Subject: RE: PROPOSAL: Consistent logging ( for 3.x, 4.x ) Date: Thu, 6 Jun 2002 10:18:57 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PROPOSAL: Consistent logging ( for 3.x, 4.x ) Thread-Index: AcIMvb1e+qg6KTqvQU2iBEQVGIcPmAAdKNhA From: "GOMEZ Henri" To: "Tomcat Developers List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >What I'm proposing is to gradually cut down to one logger API >( commons-logging ) and the 2 major implementations ( log4j and >jdk1.4 ) and the associated ( and well-documented/well known ) >config files. +1 >This may take a long time, but there are few steps that we=20 >can ( should ) take for the next releases ( 4.1.0 and 3.3.3 ). >Most of those are cosmetic ( i.e. minimal code changes ): > >1. Include log4j.jar in the distributions.=20 What about commons-logging, it's present in JTC and TC 4.0. Should it be present in TC 3.3/4.0/4.1 and JTC ? >2. In util, make o.a.t.util.Log use commons-logging as backend >by default. > >3. In 3.3, remove the configs for queue-logging. That will make >all 3.3 use the default logger, which in turns use commons-logging. > >4. Eventually provide a small fix in 4.x so that LoggerBase=20 >defaults to commons-logging if no other logger is specified, >and don't specify any logger in the config file. > >5. Same for jasper ( that's the most urgent, as it's logger >is the worst ). > >In all cases the explicit setting in server.xml will activate=20 >the current logger. > > >Long term ( for next releases ): > >- replace the use of the old loggers to direct calls to commons-log. > >- other advanced stuff, like advanced configurations=20 > >Opinions ? go go go -- To unsubscribe, e-mail: For additional commands, e-mail: