You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Mario Rodriguez Jaen (JIRA)" <ji...@apache.org> on 2014/02/06 08:40:14 UTC
[jira] [Commented] (SLING-2529) Add support for JCR Observation
event types: NODE_MOVED and PERSIST
[ https://issues.apache.org/jira/browse/SLING-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893135#comment-13893135 ]
Mario Rodriguez Jaen commented on SLING-2529:
---------------------------------------------
Besides adding those two event types to the listener, is there something else to be done at the 'handler' side? I understand that the events should be send to the *EventAdmin* once they are set with their proper resourceType and superResType.
> 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
>
> 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)