[
https://issues.apache.org/jira/browse/JCR-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152067#comment-13152067
]
Julian Reschke commented on JCR-2540:
-------------------------------------
Updated summary now that the changes for JCR-2542 provide us with node type
information:
We can now inspect the event and find out whether the node was referenceable,
and if it was, compute the local node id from the remote id; this will remove
the needed for any subsequent PROPFINDing
I believe this would also clear the remaining failure in the GetIdentifierTest.
What's not so nice is that this *only* works for referenceable nodes. For
non.referenceable nodes, we'd need the nodeId of the parent (which may be
unknown if it's removed as well).
We *might* have the parentId though if the associated event was received as
well, and we have been able to compute *that* nodeId.
Rephrasing all of this...: -)
- problem can be fixed for removal of referenceable nodes
- for other nodes we need the parentId, which might be cached (*)
(*) Doing two passes through an event bundle might help in case the events
arrive in the "wrong" order
However, if all else fails, we only have a few choices:
(1) Drop the event
(2a) Keep the event, and return null identifier (this is what happens now)
(2b) ..., and compute the identifier based on the relative path to the closest
ancestor nodeId we know; if an intermediate node *was* refererenceable, this
would be an incorrect identifier
Feedback appreciated, Julian
> 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
