Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 45205 invoked from network); 11 Dec 2002 10:04:03 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Dec 2002 10:04:03 -0000 Received: (qmail 12162 invoked by uid 97); 11 Dec 2002 10:05:17 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 12091 invoked by uid 97); 11 Dec 2002 10:05:16 -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 11926 invoked by uid 98); 11 Dec 2002 10:05:15 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-Id: <5.1.0.14.0.20021211104203.026d9be8@mail.qos.ch> X-Sender: ceki@mail.qos.ch X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 11 Dec 2002 11:04:06 +0100 To: commons-dev@jakarta.apache.org From: Ceki =?iso-8859-1?Q?G=FClc=FC?= Subject: JNDI based selection Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I have been a long time critic of commons-logging API for its class loader based approach of selecting the logging implementation. See for example my http://qos.ch/logging/thinkAgain.html document. I think more reliable solutions exist. In particular, you might want to consider the JNDI based solution discussed in http://qos.ch/logging/sc.html. I suggest that you begin reading "thinkAgain.html" first and then read sc.html. You are welcome to use the heretical ideas contained therein to your advantage or alternatively ignore them altogether. Your comments, constructive or otherwise, are welcome. Regards, -- Ceki -- To unsubscribe, e-mail: For additional commands, e-mail: