Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 81314 invoked from network); 23 Jul 2007 23:08:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jul 2007 23:08:31 -0000 Received: (qmail 47166 invoked by uid 500); 23 Jul 2007 23:08:31 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 46644 invoked by uid 500); 23 Jul 2007 23:08:30 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 46623 invoked by uid 99); 23 Jul 2007 23:08:30 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2007 16:08:30 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [208.97.132.177] (HELO spaceymail-a2.g.dreamhost.com) (208.97.132.177) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2007 16:08:28 -0700 Received: from [192.168.15.102] (cpe-76-167-142-11.socal.res.rr.com [76.167.142.11]) by spaceymail-a2.g.dreamhost.com (Postfix) with ESMTP id D5FD610A033 for ; Mon, 23 Jul 2007 16:08:07 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <0BCD2E2C-5186-417D-9EA9-A1351596C357@iq80.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: Jakarta Commons Developers List From: Dain Sundstrom Subject: [DBCP] Remove SQLNestedException Date: Mon, 23 Jul 2007 16:08:05 -0700 X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org DBCP-143 talks about problem with propagation of SQLNestedException to clients and the comment suggests a conversion to normal Java nested exception when we switch to Java 1.4. Since we made the leap, I did a bit of refactoring to remove this exception class. Basically I replace: new SQLNestedException(msg, e); with: (SQLException) new SQLException(msg).initCause(e); I attached this at a patch to 143 as I'm not 100% sure we want to go this direction. So, should we drop SQLNestedException? -dain --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org