[
https://issues.apache.org/jira/browse/SLING-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Rodriguez Jaen updated SLING-2529:
----------------------------------------
Attachment: SLING-2529-orderBefore.patch
Attached is the patch for adding the Event.MOVE to the sling resource listener.
I also added some JUnit tests for the move. I had to modify *SlingConstants*
from the sling.api package so that's why the pom is modified.
I followed the documentation in [Event Information on Move and
Order|http://www.day.com/specs/jcr/2.0/12_Observation.html] where the
Node.orderBefore should also prompt for the Event.MOVE but it was never called.
Let me know if that is the case and I'll remove the extra code to extract
those values from the Event map.
> Add support for JCR Observation event types: NODE_MOVED and PERSIST
> -------------------------------------------------------------------
>
> Key: SLING-2529
> URL: https://issues.apache.org/jira/browse/SLING-2529
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.1.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Attachments: SLING-2529-orderBefore.patch
>
>
> The JcrResourceListener does not currently support two event types added in
> the JCR 2.0 specification:
> * NODE_MOVED
> * PERSIST
> Particularly NODE_MOVED is an important event which we should support with a
> properly mapped OSGi event.
> The PERSIST event might be useful in creating event group boundaries.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
