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.


On Mon, Sep 7, 2009 at 6:47 PM, Martijn Hendriks <martijnh@gx.nl> 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,