jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1050) Remove synchronization from JNDI data sources
Date Sun, 21 Oct 2007 00:49:50 GMT

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

Jukka Zitting updated JCR-1050:

    Attachment: JCR-1050.patch

The attached patch and related files failed to apply cleanly to current trunk. I did my best
to manually apply the changes as-is, and you can find the resulting patch that covers both
modifications and new files as the JCR-1050.patch attachment. Unfortunately the patch still
doesn't even compile due to the way it handles transactions.

> Remove synchronization from JNDI data sources
> ---------------------------------------------
>                 Key: JCR-1050
>                 URL: https://issues.apache.org/jira/browse/JCR-1050
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Padraic Hannon
>         Attachments: DatasourcePersistenceManager.java, DerbyPooledPersistenceManager.java,
JCR-1050.patch, JNDI_Datasource_Changes.diff, OracleDatasourcePersistenceManager.java
> 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.

View raw message