You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominique Pfister (JIRA)" <ji...@apache.org> on 2009/07/03 14:58:47 UTC

[jira] Created: (JCR-2183) Provide overridables for lock checking

Provide overridables for lock checking
--------------------------------------

                 Key: JCR-2183
                 URL: https://issues.apache.org/jira/browse/JCR-2183
             Project: Jackrabbit Content Repository
          Issue Type: Improvement
          Components: locks
    Affects Versions: 2.0-alpha1
            Reporter: Dominique Pfister
            Assignee: Dominique Pfister
            Priority: Minor


Currently, checking whether a session is allowed to write to some locked node or whether it is allowed to unlock it is quite spread throughout the code. This should be collected to allow a custom lock manager overriding just a few methods to alter the default behavior.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JCR-2183) Provide overridables for lock checking

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2183:
-------------------------------

      Component/s: jackrabbit-core
    Fix Version/s: 2.0-alpha8

> Provide overridables for lock checking
> --------------------------------------
>
>                 Key: JCR-2183
>                 URL: https://issues.apache.org/jira/browse/JCR-2183
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, locks
>    Affects Versions: 2.0-alpha1
>            Reporter: Dominique Pfister
>            Assignee: Dominique Pfister
>            Priority: Minor
>             Fix For: 2.0-alpha8
>
>
> Currently, checking whether a session is allowed to write to some locked node or whether it is allowed to unlock it is quite spread throughout the code. This should be collected to allow a custom lock manager overriding just a few methods to alter the default behavior.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (JCR-2183) Provide overridables for lock checking

Posted by "Dominique Pfister (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominique Pfister resolved JCR-2183.
------------------------------------

    Resolution: Fixed

Fixed in revision 790892.

> Provide overridables for lock checking
> --------------------------------------
>
>                 Key: JCR-2183
>                 URL: https://issues.apache.org/jira/browse/JCR-2183
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: locks
>    Affects Versions: 2.0-alpha1
>            Reporter: Dominique Pfister
>            Assignee: Dominique Pfister
>            Priority: Minor
>
> Currently, checking whether a session is allowed to write to some locked node or whether it is allowed to unlock it is quite spread throughout the code. This should be collected to allow a custom lock manager overriding just a few methods to alter the default behavior.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.