jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-2029) JCR Remoting: Use DAV:lockroot to expose the lock-holding node
Date Thu, 27 Jun 2013 14:40:20 GMT

    [ https://issues.apache.org/jira/browse/JCR-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694760#comment-13694760

Julian Reschke commented on JCR-2029:

This is still a problem. Fixing is not totally trivial because JcrActiveLock needs a LocatorFactory
in order to compute the href for the lock holding node.
> 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
>            Assignee: Julian Reschke
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message