You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2009/03/24 11:19:51 UTC
[jira] Updated: (JCR-2030) JCR Remoting: Make usage of the
identifier-based JCR Path (283 feature)
[ https://issues.apache.org/jira/browse/JCR-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-2030:
------------------------
Component/s: (was: sandbox)
jackrabbit-spi2dav
> JCR Remoting: Make usage of the identifier-based JCR Path (283 feature)
> -----------------------------------------------------------------------
>
> Key: JCR-2030
> URL: https://issues.apache.org/jira/browse/JCR-2030
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav
> Reporter: angela
>
> spi2dav / jcr-server currently uses the "locate-by-uuid" REPORT to determine the url of a given item-based resource whose ItemId contains a unique id part.
> this could/should be simplified using the JCR Path extensions defined with JSR 283 (see also issue JCR-2028):
> - reducing # of round trips
> - get rid of uniqueId - path caches that currently don't get properly updated (see TODOs in spi2dav)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.