On 2.8.14 2:43 , Alexander Klimetschek wrote:
On 21.07.2014, at 00:23, Michael Dürig <[email protected]> wrote:
On 16.7.14 4:12 , Michael Dürig wrote:
- Path exclusion would allow certain paths to be excluded from sending
events. This is helpful if you want to listen to say /content but not to
/content/foo. Relieving event handlers from handling such exclusions
will lower client code complexity and increase performance.
I created JCR-3797 and OAK-1978 to track this.
I think it would be more useful to allow globbing paths. The current
getAdditionalPaths() could be changed to allow path globbing.
This already exists in Oak. See
org.apache.jackrabbit.oak.plugins.observation.filter.GlobbingPathFilter.
The reason this is not exposed through the API is that we still need to
maintain a certain degree of compatibility with Jackrabbit 2 and so far
we used to backport all additional features that we exposed through the
Jackrabbit API. If there is sufficient need for this feature we can
discuss adding it and clarify its support in Jackrabbit 2.
Michael
For example /home/users/**/mail/**/sentitems/**
(Could also be regular expressions)
This when you don't use very detailed node types, but rely more on path
structures. We have a lot of use cases of that in our product. I have
previously mentioned that over in [1].
[1] https://issues.apache.org/jira/browse/OAK-1133
Cheers,
Alex
r
