[SLING-6066] Clarify and complete removal resource events

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: API 2.15.0, Resource Resolver 1.5.0
• Component/s: API, ResourceResolver
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 22/Sep/16 06:39
• Updated: 07/Feb/24 18:59
• Resolved: 21/Oct/16 05:42

Description

As recently discussed in the mailing list, if a ResourceChangeListener is interested in removal events, the listener might not get the event it is interested in. For example, if the listener is registered with a glob pattern, like **.jsp, but the parent (or any parent) of a jsp is removed. In that case no removal event for the jsp itself is sent. Which means the listener is unaware of removals.

We need to clarify this in the javadocs, but also should implement handling removal in the following:
If a listener is registered for removal events - regardless if a glob pattern is used or not - the listener will be notified of removals of any parent node up to the top level node. For example if a listener is interested in /a/b/c/*/.jsp, a removal of any resource below "c", but also removal of "a", "b", or "c" is reported to the listener.

Issue Links

• blocks: SLING-5994 Move from EventHandler to new ResourceChangeListener API
• is related to: SLING-12245 Sling Rewriter does not detect configuration changes coming in via move
• is related to: SLING-12249 Clarify "ADDED" resource changes for ancestor nodes of path