From open-jpa-dev-return-1728-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Mon Jan 22 22:07:27 2007 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 23451 invoked from network); 22 Jan 2007 22:07:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jan 2007 22:07:26 -0000 Received: (qmail 1324 invoked by uid 500); 22 Jan 2007 22:07:33 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 1220 invoked by uid 500); 22 Jan 2007 22:07:32 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 1211 invoked by uid 99); 22 Jan 2007 22:07:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jan 2007 14:07:32 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of awhite@bea.com designates 66.248.192.21 as permitted sender) Received: from [66.248.192.21] (HELO usremg01.bea.com) (66.248.192.21) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jan 2007 14:07:24 -0800 Received: from usremr02.bea.com (usremr02.bea.com [10.160.29.92]) by usremg01.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l0MM6x1d025641 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 22 Jan 2007 14:07:03 -0800 Received: from [10.0.1.9] ([10.43.242.66]) by usremr02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l0MM6vPb014032 for ; Mon, 22 Jan 2007 14:06:57 -0800 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <89c0c52c0701221336l4fa46946p1e60229a01b01c67@mail.gmail.com> References: <7a5e6f6a0701221101n1ba36d3cm1d2a7b57ad2c0784@mail.gmail.com> <89c0c52c0701221336l4fa46946p1e60229a01b01c67@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Abe White Subject: Re: openjpa logging Date: Mon, 22 Jan 2007 16:06:48 -0600 To: open-jpa-dev@incubator.apache.org X-Mailer: Apple Mail (2.752.3) X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2007.1.2.131432 X-Virus-Checked: Checked by ClamAV on apache.org > So the assumption is that the caller will log the appropriate > exception-related message if such an exception is caught? We're throwing an exception. The user has to do something with it. It is a trivial matter for him to log it if that's what he chooses to do, but I would expect much more sophisticated handling of exceptions by most users -- handling based on the operation in question and what behavior might be expected. > The processing that I am used to is to log any unexpected > exceptions when > calling out to an external plugin or feature. All exceptions we encounter are unexpected. We can't tell the difference between a database error caused by the user's illegal actions and one caused by an internal database error. In my experience, you either throw an exception or log it. When you do both, you just end up with repeats of the same exception logged repeatedly as it propagates. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.