[SLING-5837] Allow ResourceChangeListeners to define glob patterns for resource matching

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: API 2.12.0
• Fix Version/s: API 2.14.0
• Component/s: API
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 12/Jul/16 14:08
• Updated: 07/Dec/16 15:00
• Resolved: 20/Jul/16 15:21

Description

While the previous way to interact with Resource change events through registering EventHandler sevices allowed defining glob patterns for matching the watched paths, the current state of the org.apache.sling.api.resource.observation.ResourceChangeListener only allows subscribing to events for concrete paths.

In order to allow for the same filtering flexibility, ResourceChangeListener should also accept glob patterns for its resource.paths configuration property.

Issue Links

• blocks: SLING-5252 Remove getAdministrativeResourceResolver() from Scripting Core
• blocks: SLING-5253 Remove getAdministrativeResourceResolver() from the Sightly engine
• is related to: SLING-6350 Incorrect matching in Path class causes MountByFS to fail (more than 2 slashes fails)
• relates to: SLING-5903 ResourceChangeListenerInfo does not expand glob patterns correctly