[
https://issues.apache.org/jira/browse/JCR-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated JCR-4044:
-----------------------------
Attachment: JCR-4044.v2.patch
Attaching a very raw sketch [^JCR-4044.v2.patch] which is actually oak code
that would add an oak-jcr utility class instead of extending the
{{JackrabbitEventFilter}}:
* {{EventFilterBuilder}} : {{public static JackrabbitEventFilter
orGlobPath(JackrabbitEventFilter baseFilter, String globPath)}}
The advantage of this approach is that it leaves Jackrabbit unchanged and that
it doesn't leave users of the JackrabbitEventFilter wondering whether or not
this feature is supported (for Jackrabbit it would probably not be supported,
for Oak it would).
/cc [~mduerig]
> Support glob patterns through JackrabbitEventFilter
> ---------------------------------------------------
>
> Key: JCR-4044
> URL: https://issues.apache.org/jira/browse/JCR-4044
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: core
> Reporter: Carsten Ziegeler
> Attachments: JCR-4044.patch, JCR-4044.v2.patch
>
>
> In the Sling project, we would like to register JCR listeners based on glob
> patterns as defined in
> https://jackrabbit.apache.org/oak/docs/apidocs/org/apache/jackrabbit/oak/plugins/observation/filter/GlobbingPathFilter.html
> So basically instead (or in addition) to specifying an absolute path,
> defining patterns.
> [Discussion
> thread|https://lists.apache.org/thread.html/300f84574bbb039cebe35aab1afc21e043560a1c0471e456a2f5c0be@%3Cdev.jackrabbit.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
