Return-Path: Delivered-To: apmail-jakarta-struts-dev-archive@apache.org Received: (qmail 30102 invoked from network); 16 Jan 2002 03:12:44 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 16 Jan 2002 03:12:44 -0000 Received: (qmail 13621 invoked by uid 97); 16 Jan 2002 03:12:43 -0000 Delivered-To: qmlist-jakarta-archive-struts-dev@jakarta.apache.org Received: (qmail 13591 invoked by uid 97); 16 Jan 2002 03:12:42 -0000 Mailing-List: contact struts-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list struts-dev@jakarta.apache.org Received: (qmail 13570 invoked from network); 16 Jan 2002 03:12:40 -0000 Date: Tue, 15 Jan 2002 18:50:01 -0800 (PST) From: "Craig R. McClanahan" To: struts-dev@jakarta.apache.org Subject: Proposed Migration to DBCP Based Connection Pool Message-ID: <20020115184752.I57179-100000@icarus.apache.org> 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 I am going to propose that we switch to a connection pool based on the commons-dbcp (and commons-pool) packages as the "preferred" data source implementation for Struts 1.1. The existing implementation already has equivalent functionality to what org.apache.struts.util.GenericDataSource covers, and it will shortly have some additional very useful things (such as caching PreparedStatement instances for reuse). Towards that end, I'm adding dependencies in the Struts build scripts for commons-dbcp.jar and commons-pool.jar. You'll want to update your build environments to include definitions for these properties. Craig -- To unsubscribe, e-mail: For additional commands, e-mail: