jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2029) JCR Remoting: Use DAV:lockroot to expose the lock-holding node
Date Tue, 24 Mar 2009 10:19:51 GMT

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

angela updated JCR-2029:
------------------------

    Component/s:     (was: sandbox)
                 jackrabbit-spi2dav

> JCR Remoting: Use DAV:lockroot to expose the lock-holding node
> --------------------------------------------------------------
>
>                 Key: JCR-2029
>                 URL: https://issues.apache.org/jira/browse/JCR-2029
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-server, jackrabbit-spi2dav
>            Reporter: angela
>
> for deep locks discovered on a lock within the locked subtree spi2dav currently needs
to retrieve the lockdiscovery multiple times in order to determine the lock holding node.
> if the JcrActiveLock would include the DAV:lockroot element LockInfo.getNodeId could
always be determined without any need for additional PROPFIND calls.

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


Mime
View raw message