Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 31124 invoked from network); 31 Oct 2001 22:12:19 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 31 Oct 2001 22:12:19 -0000 Received: (qmail 6993 invoked from network); 31 Oct 2001 22:14:35 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 31 Oct 2001 22:14:35 -0000 Received: (qmail 911 invoked by uid 97); 31 Oct 2001 22:12:04 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 756 invoked by uid 97); 31 Oct 2001 22:12:02 -0000 Mailing-List: contact avalon-dev-help@jakarta.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 avalon-dev@jakarta.apache.org Received: (qmail 732 invoked from network); 31 Oct 2001 22:12:01 -0000 Message-Id: <200110312212.f9VMBx219287@mail016.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Avalon Developers List" Subject: Re: Check this alternative to Loggable Date: Thu, 1 Nov 2001 05:45:27 +1100 X-Mailer: KMail [version 1.3.1] References: <3BDF11A6.FA86E94F@apache.org> In-Reply-To: <3BDF11A6.FA86E94F@apache.org> X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 Wed, 31 Oct 2001 07:46, Berin Loritsch wrote: > I updated the Loggable proposal. This provides a smooth upgrade to the > new Logger interface instead of the LogKit Logger implementation. By smooth you mean non backwards compayible and will break your existings systems ? ;) I am fairly anti such a move. I would much much much prefer something like the following. This is binary compatible and will not force me to go through and change oodles of stuff. interface LogAware { void enableLogging( Logger ); } class abstract AbstractLogAware implements LogAware {} I really don't think we should be breaking binary compatability in such a fundamental interface in a supposedly stable library. > The AbstractLogger will perform the wrapping for you. > > Let me know what you all think, as I want to get this in ASAP! -- Cheers, Pete *------------------------------------------------------* | Hlade's Law: If you have a difficult task, give it | | to a lazy person -- they will find an easier | | way to do it. | *------------------------------------------------------* -- To unsubscribe, e-mail: For additional commands, e-mail: