[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517311
]
Padraic Hannon commented on JCR-1050:
-------------------------------------
Yeah I saw that in the code. However, from what I can tell the only place where
the connection autocommit is explicitly turned off and rollback() and commit()
are called is in the method store(ChangeLog). Assuming that one is running in a
container and has access to a datasource I would also assume that one has
access to a UserTransaction object. If that is the case, rather than using a
connection's transaction handling one can delegate the transaction handling to
jta.
> Remove synchronization from JNDI data sources
> ---------------------------------------------
>
> Key: JCR-1050
> URL: https://issues.apache.org/jira/browse/JCR-1050
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3,
> 1.3.1, 1.4, 2.0
> Reporter: Padraic Hannon
>
> Using datasources one should be able to rely on the application server to
> manage PreparedStatement caches therefore pre-creating and holding onto the
> connection for long periods of time should not be needed. This relates to
> improvement JCR-313, however, that change did not address the benefits one
> could see in using an application server controlled datasource. Even if
> jackrabbit does aim to use an embedded database such a system could be
> configured to use datasources and could benefit from the removal of the
> synchronization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
