Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 36091 invoked from network); 7 Mar 2002 06:23:22 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 Mar 2002 06:23:22 -0000 Received: (qmail 24576 invoked by uid 97); 7 Mar 2002 06:23:31 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 24541 invoked by uid 97); 7 Mar 2002 06:23:30 -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 24530 invoked from network); 7 Mar 2002 06:23:30 -0000 Message-ID: <016801c1c5a1$47ae5b20$c77ba8c0@frmt1.sfba.home.com> From: "Martin Cooper" To: "Jakarta Commons Developers List" References: <921E60ADEB30D84EACA350AD31A1FD7506E31E@chiex02> Subject: Re: commons dbcp or pool problems Date: Wed, 6 Mar 2002 22:28:22 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Waldhoff, Rodney" To: "'Jakarta Commons Developers List '" Sent: Wednesday, March 06, 2002 4:27 AM Subject: RE: commons dbcp or pool problems > > What is the status of commons dbcp? > > Is this considered done > > and production quality or it still in beta (or less?) > > IMO, commons-dbcp is production quality, indeed, I use it for a number > of > production applications. We could do a 1.0 release pretty much anytime, > although the documentation is probably insufficient, and the JOCL > configuration should probably either be converted to digester or > something > like it, or JOCL moved to a stand-alone component. What do you have in mind with regard to Digester-based configuration? I'd be willing to take a crack at doing this if you could give me some pointers on what you'd like to see. Bear in mind that I'm not exactly a JOCL expert. ;-) I have a vested interest in seeing DBCP released soon, because we're going to be releasing Struts 1.1 soon, and that relies on it... -- Martin Cooper > > > Apart from what look like minor > > edits from Craig, it's been 10 months > > (according to CVS) since any major > > work has been done. > > And one could see that as a good thing. > > There was some talk on this list a few weeks back about some minor > enhancments to DBCP/Pool (like having the pool methods throw Exception, > allowing DBCP to propogate the original SQLExceptions, etc.) but no > patches > materialized out of that discussion. > -- To unsubscribe, e-mail: For additional commands, e-mail: