You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Padraic Hannon (JIRA)" <ji...@apache.org> on 2007/08/02 18:22:53 UTC
[jira] Updated: (JCR-1050) Remove synchronization from JNDI data
sources
[ https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Padraic Hannon updated JCR-1050:
--------------------------------
Attachment: JNDI_Datasource_Changes.diff
Diff file with non-synchronized JNDI datasources.
> 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
> Attachments: JNDI_Datasource_Changes.diff
>
>
> 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.