Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 67425 invoked from network); 15 Sep 2003 21:42:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 15 Sep 2003 21:42:54 -0000 Received: (qmail 76621 invoked by uid 500); 15 Sep 2003 21:42:38 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 76606 invoked by uid 500); 15 Sep 2003 21:42:38 -0000 Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Users List" Reply-To: "Apache Torque Users List" Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 76593 invoked from network); 15 Sep 2003 21:42:38 -0000 Received: from unknown (HELO mail1.digitaldist.net) (4.38.41.136) by daedalus.apache.org with SMTP; 15 Sep 2003 21:42:38 -0000 Subject: RE: external DB connection pool access Date: Mon, 15 Sep 2003 14:42:44 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <86B62B910F925F429E6A61B4C6F3B0570158D734@mail1.digitaldist.net> content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: external DB connection pool access Thread-Index: AcN7zpe1hgW+b243S9yMebUezKbXMQAAzmWA From: "Gary Baker" To: "Apache Torque Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Matt, Thanks a bunch. We were using JNDI for the other apps, so that worked for me perfectly! Cheers, Gary -----Original Message----- From: Matt Hughes [mailto:mhughe@uvic.ca]=20 Sent: Monday, September 15, 2003 2:16 PM To: Apache Torque Users List Subject: Re: external DB connection pool access On Mon, 15 Sep 2003, Gary Baker wrote: > I want to setup Torque to use an external DB connection pool.=20 > Basically, we have a group of applications running under one instance=20 > of Tomcat and all the other applications (besides my new Turbine app.) > use the same connection pool. You may wish to examine JNDI (Java Network Directory Interface). JNDI provides a way of configuring a data source and giving it a name, which can be access by Torque. JNDI background: http://java.sun.com/products/jndi/ For information about setting up Tomcat to create a JNDI database connection, see: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples -howto.html http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.htm l To use a JNDI pool with Torque, see: http://db.apache.org/torque/configuration-howto.html Depending on how the pool the other applications use works, some changes may be needed to use JNDI, or it may be completly impractical. Note that I have not used JNDI, so I can't really say how well this would work. If I've misunderstood and you want to add another type of pool to Toruqe, then you should probably look at how org.apache.torque.dsfactory.SharedPoolDataSourceFactory and friends are implemented, and cook up some new pool code based on that. Then you should be able to just put your new pool class name in your property file for the torque.dsfactory.XXX.factory property. mch mhughe@uvic.ca --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org