Return-Path: Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 11369 invoked by uid 500); 11 Jun 2003 13:38:47 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 11303 invoked from network); 11 Jun 2003 13:38:46 -0000 Received: from onramp.i95.net (205.177.132.17) by daedalus.apache.org with SMTP; 11 Jun 2003 13:38:46 -0000 Received: from apache.org ([66.208.12.130]) by onramp.i95.net (8.12.9/8.12.9) with ESMTP id h5BDcl07005426 for ; Wed, 11 Jun 2003 09:38:47 -0400 Message-ID: <3EE7312A.9060403@apache.org> Date: Wed, 11 Jun 2003 09:39:54 -0400 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: avalon-excalibur/logger refactoring References: <14327835605.20030611165206@mail.cnt.ru> In-Reply-To: <14327835605.20030611165206@mail.cnt.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Anton Tagunov wrote: > Hello, Gentlemen! > > Have just completed putting into the cvs > my thoughts on *LoggerManager design. > > Maybe I was in too much hurry to commit > this to cvs right away, but anyhow the > code is already there. > > I would like you to have a look a give > you comments. > > Please start at the > avalon-excalibur/logger/src/java/o/a/a/e/logger/Facade.java > and proceed to > avalon-excalibur/logger/src/java/o/a/a/e/logger/logkit/*.java > avalon-excalibur/logger/src/java/o/a/a/e/logger/log4j/*.java > avalon-excalibur/logger/src/java/o/a/a/e/logger/decorators/*.java > > > I hope that I have learned something from the designs > in other parts of the system and here is the result :-) > > -=--------------- > > The motivation was that > > * LogKitLoggerManager was getting crafty > > * there were disagreements on whether for instance the root > logger obtained from the LoggerManager > (getDefaultLogger() and getLoggerForCategory("")) > should be overrideable or not I'm glad you are taking on the task of making it work well. That's a good thing. Please do keep in mind that this package is used by more than one project, so please make sure that we have backwards compatibility. There is nothing wrong with clarifying some issues in the classes, but if we change classnames, etc. we need to make sure that the LoggerManager stuff still works. Cocoon uses it, so when you are done with your refactoring work, I'd like to test dropping it in Cocoon to make sure nothing breaks. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org