[
https://issues.apache.org/jira/browse/DBCP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DBCP-382.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0
1.5.1
Thanks for the report and the patch. Sorry it has taken so long to apply it.
I've applied the patch to trunk for the 2.x series and to the 1.5.x branch. It
will be included in the next release of each.
If there are further 1.3.x and 1.4.x releases (currently being discussed on the
dev mailing list) my expectation is that they will be generated from the 1.5.x
branch so will pick up this fix too.
> Could not set flag "accessToUnderlyingConnectionAllowed" in "context.xml" for
> DriverAdapterCPDS/PerUserPoolDataSource
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DBCP-382
> URL: https://issues.apache.org/jira/browse/DBCP-382
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Apache Tomcat 6.0.32 / DBCP 1.3
> Reporter: Stefan Rempfer
> Fix For: 1.5.1, 2.0
>
>
> Could not set flag "accessToUnderlyingConnectionAllowed" in context.xml for
> DriverAdapterCPDS/PerUserPoolDataSource because the property is not
> considered from the factory.
> A possible solution is to add following lines to class "DriverAdapterCPDS" on
> the end of method "getObjectInstance"
> {code}
> ra = ref.get("accessToUnderlyingConnectionAllowed");
> if (ra != null && ra.getContent() != null) {
>
> setAccessToUnderlyingConnectionAllowed(Boolean.valueOf(ra.getContent().toString()).booleanValue());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
