[
https://issues.apache.org/jira/browse/CONFIGURATION-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-412.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.7
A fix was applied in SVN revision 931667 (and also ported to the configuration2
branch).
{{DatabaseConfiguration}} now provides additional constructors that allow
setting a flag whether commits should be performed on the connection obtained
from the data source. Per default, this flag is *false*, so that the behavior
of the configuration class is not changed when using the old constructors.
Note that we currently do not perform a rollback if an exception occurs. This
does not seem to be necessary.
> Cannot use DatabaseConfiguration if the datasource has autocommit = false
> -------------------------------------------------------------------------
>
> Key: CONFIGURATION-412
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-412
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Windows / Linux - Database Oracle 11
> Reporter: Stefano Bertini
> Assignee: Oliver Heger
> Priority: Critical
> Fix For: 1.7
>
>
> If using a DatabaseConfiguration object with a datasource that has
> *autocommit = false*, the setProperty method fails with a *duplicate key*
> error.
> This happens because in the setProperty method the two calls
> _clearProperty(key)_ and _addProperty(key, value)_ can retrieve two different
> connections from the database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
