Hi, If you use a JNDI DataSource (by using a javax.naming.Context class as the driver in the descriptors) then that DataSource is used as-is. The only change then is that Connection instances are not cached anymore in the DB components (e.g. BundleDbPersistenceManager). Instead, they are retrieved on-demand from the JNDI DataSource. Does that address your point?
Best regards, Martijn From: Guo Du [mailto:[email protected]] Sent: Monday, September 07, 2009 10:19 PM To: [email protected] Subject: Re: JCR 1456 Database connection pooling If connections pools works as an optional configuration for db pm, should be fine. Pool management is not needed at some circumstance, such as container managed datasource connections pool. Thanks! --Guo On Mon, Sep 7, 2009 at 6:47 PM, Martijn Hendriks <[email protected]<mailto:[email protected]>> wrote: Hi Thomas, Existing configurations (i.e., repository and workspace descriptors) do not have to be changed to work with the patch. You do need the commons-dbcp library on your classpath though because also for existing configurations the behavior is changed: instead of caching a Connection locally (in e.g. the DbBundlePMs), it is retrieved every time it is needed from a pooling DataSource. Best regards, Martijn
