[
https://issues.apache.org/jira/browse/SLING-12246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814722#comment-17814722
]
Carsten Ziegeler commented on SLING-12246:
------------------------------------------
Sure. In theory there should be no need to handle a move event. But if there
are cases where no added/removed combo is sent, then this should probably be
fixed (best in Oak).
> Support Event.NODE_MOVED in JcrResourceListener
> -----------------------------------------------
>
> Key: SLING-12246
> URL: https://issues.apache.org/jira/browse/SLING-12246
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 3.2.4
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently the event type NODE_MOVED
> (https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/12_Observation.html#12.3.3%20Event%20Information%20on%20Move%20and%20Order)
> is not supported in {{JcrResourceListener}}
> (https://github.com/apache/sling-org-apache-sling-jcr-resource/blob/8fb5a3d44de01f05964028debcf24531f2f65747/src/main/java/org/apache/sling/jcr/resource/internal/JcrResourceListener.java#L117).
> Although the support in Oak is limited
> (https://jackrabbit.apache.org/oak/docs/differences.html#observation) the
> even type is still used.
> IMHO it should be translated into two {{ResourceChange}} events:
> # one change on the source path
> # one change on the destination path
> The path handling for
> https://sling.apache.org/apidocs/sling12/org/apache/sling/api/resource/observation/ResourceChangeListener.html#PATHS
> must be the same as for remove events (i.e. changed parent paths will also
> trigger it)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
