[jira] Commented: (JCR-1050) Remove synchronization from JNDI data sources

["Dominique Pfister (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517182 ] 

Dominique Pfister commented on JCR-1050:
----------------------------------------

I'm afraid, letting the application server manage the database connection is not an option: database persistence managers in JR need to control the database connection and tell when to commit or rollback. Whenever some change needs to be saved, a PM will first put the connection to manual commit mode and then write all changes in one transaction. If some application server would control the connection lifecycle, the in-memory representation of content and the one in the database could get out of sync.


> 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.