That it's registered with JNDI does not help. But perhaps what is really meant is "configure your pool through Tomcat's built-in support for DBCP (which uses JNDI)". Then you'd get whatever management of the pool that Tomcat brings (for example, when the webapp is shutdown, it will .close() the pool itself, which perhaps you'd forget to do, if you manage your own pooling). But other than that, I can't think of what advantage it would bring.
> -----Original Message----- > From: Alex Turner [mailto:[EMAIL PROTECTED] > Sent: Monday, January 23, 2006 11:54 AM > To: Tomcat Users List > Subject: Re: Connection Pool Woes > > > How does registering my pooling datasource with a naming > directory help connection management? (Honest question - I > really don't know) > > Alex. > > On 1/23/06, Asad Habib <[EMAIL PROTECTED]> wrote: > > You should use JNDI with your connection pool to ensure that > > connections are being managed appropriately. > > > > - Asad > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
