Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 96662 invoked by uid 500); 2 Oct 2001 12:59:30 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 96646 invoked from network); 2 Oct 2001 12:59:25 -0000 Importance: Normal Subject: Re: log4j should be pluggable To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: From: "Sam Ruby" Date: Tue, 2 Oct 2001 09:00:22 -0400 X-MIMETrack: Serialize by Router on D04NM301/04/M/IBM(Release 5.0.8 |June 18, 2001) at 10/02/2001 08:58:58 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Russell Butek wrote: > > Nothing against log4j (well, not much), but the AXIS logging mechanism > should be pluggable. This discussion must have taken place just before you joined. In essence, the reasoning was: (1) We need a pluggable logging facility. That much is agreed. (2) Log4j already has a pluggable ability to add in your own "appenders". Designed. Tested. Documented. Supported. People (like MacroMedia) have used this successfully to direct output to their own logging facility. (3) If we were to write our own wrapper for logging, would it be better designed, tested, documented, or supported than the facility already in log4j? - Sam Ruby