Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 29422 invoked from network); 25 Jul 2002 18:41:26 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Jul 2002 18:41:26 -0000 Received: (qmail 25345 invoked by uid 97); 25 Jul 2002 18:41:45 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 25329 invoked by uid 97); 25 Jul 2002 18:41:44 -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 25317 invoked by uid 98); 25 Jul 2002 18:41:44 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: Re: [Logging] more issues with stack reading From: Bob Herrmann To: Jakarta Commons Developers List In-Reply-To: <3D404096.5090900@sun.com> References: <3D404096.5090900@sun.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 25 Jul 2002 14:44:32 -0400 Message-Id: <1027622672.28115.44.camel@dhcp-70-230> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, 2002-07-25 at 14:16, Patrick Luby wrote: > Costin and Bob, > > costinm@covalent.net wrote: > > > > The problem we're having is support for the old wrappers in > > tomcat, as we need to filter them out too. We're trying to > > get commons-logging used everywhere, but keep backward > > compatibility since the Logger/Log interface is part of the > > tomcat APIs. > > > > I may be missing something, but would a possible approach be to change > all of the Logger/Log interface calls to commons-logging in the new > version of Tomcat (i.e. jakarta-tomcat-5). Since this is a very new > workspace, it seems the safest place to make the switch (messing with > Tomcat 4.x seems too risky to me). This would eliminate the need to put > in a Tomcat-specific class into commons-logging. > > What do you think? $ cd jakarta-tomcat-4.0 $ grep -i -l 'void.*log(' `find . -name *.java`|wc -l 65 Looks like 65 classes need to be beaten into using commons-logging. I will take a stab at this and see if it is simply cut/past/click/drag or if other nasty issues start popping up. Learn by doing, yippie. :-) Cheers, -bob -- To unsubscribe, e-mail: For additional commands, e-mail: