openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <>
Subject [jira] Updated: (OPENJPA-1764) Automatically enable connection pooling in unmanaged environments
Date Tue, 28 Sep 2010 15:30:32 GMT


Donald Woods updated OPENJPA-1764:

    Attachment: OPENJPA-1764-20100927.diff

Code to introduce automatic usage of Commons DBCP for Java SE apps in a non-managed and non-transaction
setup, when Commons DBCP is on the class path.
The default behavior is -
but users can force usage of DBCP or fail if it not available by setting -
or force the old behavior of using the ConnectionDriverName as-is by setting -

The openjpa.ConnectionProperties setting can be used to provide Commons DBCP arguments, like
but the DBCPDriverDataSource will use the following defaults if none are provided -

> Automatically enable connection pooling in unmanaged environments
> -----------------------------------------------------------------
>                 Key: OPENJPA-1764
>                 URL:
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: jdbc, performance
>    Affects Versions: 2.1.0
>            Reporter: Donald Woods
>            Assignee: Donald Woods
>             Fix For: 2.1.0
>         Attachments: OPENJPA-1764-20100927.diff
> When commons-dbcp is present on the classpath and we are running in a JSE or unmanaged
environment, we should automatically configure DriverClassName=org.apache.commons.dbcp.BasicDataSource
and apply some DBCP args (this might be the tricky part, based on the different dbcp args
we have to use today for different databases...)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message