[
https://issues.apache.org/jira/browse/SLING-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434694#comment-15434694
]
Chetan Mehrotra commented on SLING-5994:
----------------------------------------
[~hanishbansal93] While you work on changes can you also review what kind of
stuff this handler are listening for. Can there be other criteria apart from
path on which resource change events can be filtered for e.g. change happening
on resource having specific nodetype, property etc
If there is a common pattern then we can further optimize the filtering at Oak
level (and possibly at Sling level) via support for nodetype based filtering
OAK-4586
[~cziegeler] [~egli] May we can provide more filtering parameters which allow
event send to avoid doing hard work if possible
> Move from Deprecated EventHandler to new ResourceChangeListener API
> -------------------------------------------------------------------
>
> Key: SLING-5994
> URL: https://issues.apache.org/jira/browse/SLING-5994
> Project: Sling
> Issue Type: Task
> Components: API
> Reporter: Hanish Bansal
>
> This issue serves as the container for the issues for migrating all
> implementations of EventHandler to new Resource Observation API in Sling Code.
> The new API that listens to the resource events is :
> https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChangeListener.java
> API for the Resource Change Events :
> https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChange.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
