[
https://issues.apache.org/jira/browse/JCR-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-2029:
--------------------------------
Fix Version/s: 2.7.1
2.6.3
2.4.5
Priority: Minor (was: Major)
Affects Version/s: 2.4.4
2.6.2
2.7
> 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
> Affects Versions: 2.4.4, 2.6.2, 2.7
> Reporter: angela
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.4.5, 2.6.3, 2.7.1
>
>
> 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
