You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Commented) (JIRA)" <ji...@apache.org> on 2011/11/04 18:13:51 UTC
[jira] [Commented] (JCR-2540) spi2dav : move/reorder not properly
handled by observation
[ https://issues.apache.org/jira/browse/JCR-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144176#comment-13144176 ]
Julian Reschke commented on JCR-2540:
-------------------------------------
The remaining issue is caused by NODE_REMOVE events not having an identifier.
Identifiers are currently generated by the URIResolver, based on the URI of the node reported in the event. The URI resolver then does a PROPFIND, asking for the UUID, the local name (unescaped), and the index, from which a local identifier is built.
This, of course, doesn't work for nodes that were just deleted (unless the information happens to be cached).
As a matter of fact, the events returned by the server *do* contain the server's identifier for that event. Unfortunately, these identifiers are no quite the same as those needed in spi2dav, which only uses UUID-style identifiers for referenceable nodes, while jackrabbit-core uses them throughout.
The obvious fix would be to augment the event information sent by the server with more information, so that the subsequent PROPFIND is never needed.
Putting this on hold while looking at the other observation related tickets...
> spi2dav : move/reorder not properly handled by observation
> ----------------------------------------------------------
>
> Key: JCR-2540
> URL: https://issues.apache.org/jira/browse/JCR-2540
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, JCR 2.0, observation
> Affects Versions: 2.0
> Reporter: angela
> Assignee: Julian Reschke
>
> all TCK tests including move or reorder fail in the setup jcr2spi - spi2dav(ex) - jcr-server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira