You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2010/11/11 16:33:14 UTC
[jira] Created: (JCR-2811) Allow to override LockManager creation
Allow to override LockManager creation
--------------------------------------
Key: JCR-2811
URL: https://issues.apache.org/jira/browse/JCR-2811
Project: Jackrabbit Content Repository
Issue Type: New Feature
Components: jackrabbit-core
Reporter: Thomas Mueller
Assignee: Thomas Mueller
Fix For: 2.2.0
Currently, Repository.getLockManager() internally creates a new lock manager if needed.
Jackrabbit should provide an extension point so that a JCR repository that extends it can create a custom lock manager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2811) Allow to override LockManager creation
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller resolved JCR-2811.
---------------------------------
Resolution: Fixed
Implemented in the trunk.
> Allow to override LockManager creation
> --------------------------------------
>
> Key: JCR-2811
> URL: https://issues.apache.org/jira/browse/JCR-2811
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 2.2.0
>
>
> Currently, Repository.getLockManager() internally creates a new lock manager if needed.
> Jackrabbit should provide an extension point so that a JCR repository that extends it can create a custom lock manager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.