[
https://issues.apache.org/jira/browse/SLING-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379031#comment-15379031
]
Radu Cotescu commented on SLING-5837:
-------------------------------------
Let me try to answer punctually:
# I've thought that glob pattern matching is a subset of the LDAP filter syntax
used by OSGi {{EventHandlers}} so it felt rather natural to enhance the
{{ResourceChangeListeners}} filtering support;
# yes, you're right; I guess I was too trigger happy;
# we can definitely optimise that;
Should we cancel the release and address your concerns? What do you propose for
1?
> Allow ResourceChangeListeners to define glob patterns for resource matching
> ---------------------------------------------------------------------------
>
> Key: SLING-5837
> URL: https://issues.apache.org/jira/browse/SLING-5837
> Project: Sling
> Issue Type: Improvement
> Components: API
> Affects Versions: API 2.12.0
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Fix For: API 2.13.0
>
> Attachments: SLING-5837.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
