Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 3921 invoked from network); 5 Feb 2002 11:51:00 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 5 Feb 2002 11:51:00 -0000 Received: (qmail 9840 invoked by uid 97); 5 Feb 2002 11:49:44 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 9824 invoked by uid 97); 5 Feb 2002 11:49:43 -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 9776 invoked from network); 5 Feb 2002 11:49:34 -0000 Message-ID: <903A7281CDB7D4118A5000500450BB0838395A@samoa.sitewaerts> From: Daniel Hoppe To: 'Jakarta Commons Developers List' Subject: RE: Problems with commons-logging Date: Tue, 5 Feb 2002 12:50:23 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >=20 > I've been thinking about this. The situation you're outlining=20 > goes something > like this at the code level: >=20 > if (someHorribleCondition) { > log.error("Bad Things Happened Here"); > //Now what? > } >=20 > If the //Now what? doesn't include a thrown exception, but it's = severe > enough to cause the application using the compenent to fail,=20 > the component > has a real problem, not just a logging issue. >=20 > Now, maybe the debug level of logging might provide enough=20 > insight to debug > the problem, but that's not a good default for unconfigured logging. >=20 I've been searching for errors which came from "this-should-never-happen"-conditions several times, it's not really = fun to debug. I think if a "this-should-never-happen" actually occurs, the application/component/method should at least try something which is = likely to work, e.g. print the stacktrace to console. Daniel <<<<<<<<<<<<<<<<<<<<<<<<<<< sitewaerts GmbH Hebelstra=DFe 15 D-76133 Karlsruhe Tel: +49 (721) 920 918 0 Fax: +49 (721) 920 918 29 http://www.sitewaerts.de >>>>>>>>>>>>>>>>>>>>>>>>>>> -- To unsubscribe, e-mail: For additional commands, e-mail: