[SLING-12246] Support Event.NODE_MOVED in JcrResourceListener

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: JCR Resource 3.2.4
• Component/s: JCR
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 06/Feb/24 10:17
• Updated: 01/Mar/24 11:19
• Resolved: 01/Mar/24 11:19

Description

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:

1. one change on the source path
2. 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)

Issue Links

• is related to: SLING-12245 Sling Rewriter does not detect configuration changes coming in via move
• links to: GitHub Pull Request #41