[
https://issues.apache.org/jira/browse/JCR-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2540:
----------------------------------
Attachment: JCR-2540.patch
I think, I would do it on a best effort basis and build a path based identifier
for the event in case the URI cannot be translated into a UUID based identifier.
See proposed patch.
> 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
> Attachments: JCR-2540.patch
>
>
> 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
