Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 97237 invoked from network); 25 Jun 2003 16:25:48 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 25 Jun 2003 16:25:48 -0000 Received: (qmail 20187 invoked by uid 97); 25 Jun 2003 16:28:11 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 20180 invoked from network); 25 Jun 2003 16:28:11 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 25 Jun 2003 16:28:11 -0000 Received: (qmail 96983 invoked by uid 500); 25 Jun 2003 16:25:45 -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 96964 invoked from network); 25 Jun 2003 16:25:44 -0000 Received: from icarus.apache.org (208.185.179.13) by daedalus.apache.org with SMTP; 25 Jun 2003 16:25:44 -0000 Received: (qmail 69384 invoked by uid 1304); 25 Jun 2003 16:25:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Jun 2003 16:25:44 -0000 Date: Wed, 25 Jun 2003 09:25:43 -0700 (PDT) From: Rodney Waldhoff To: Jakarta Commons Developers List , dgraham@apache.org Subject: Re: Checked vs Runtime exceptions In-Reply-To: <20030625145806.62867.qmail@web20706.mail.yahoo.com> Message-ID: <20030625091845.R4842@icarus.apache.org> References: <20030625145806.62867.qmail@web20706.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N 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, 25 Jun 2003, David Graham wrote: > Logging was merely an example (probably a poor one). Agreed. Logging was one of my examples, and it's a bad one for the sake of this discussion. In practice no logging API I'm aware throws Runtime or checked Exceptions, but silently fail as far as the calling code is concerned, and perhaps attempt to report the failure to the user via some other channel. Indeed given that the actual logging typically happens asynchronously, this is pretty much the only possible strategy, on top of being the most desirable one. For the remainder of this discussion can we drop the logging example? There's still three (or two, depending upon how you factor it) concrete examples out there. - Rod --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org