You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Oliver Lietz (JIRA)" <ji...@apache.org> on 2016/07/13 10:58:20 UTC

[jira] [Commented] (SLING-5837) Allow ResourceChangeListeners to define glob patterns for resource matching

    [ https://issues.apache.org/jira/browse/SLING-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374831#comment-15374831 ] 

Oliver Lietz commented on SLING-5837:
-------------------------------------

Our paths are resource (JCR) paths and _not_ file system paths. So I have concerns regarding the implementation as it uses classes from {{java.nio.file}} which are platform dependent and _may_ lead to different results. Can we rule out such cases?

* https://docs.oracle.com/javase/tutorial/essential/io/find.html
* http://docs.oracle.com/javase/7/docs/api/java/nio/file/FileSystem.html

> 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)