You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/10/30 09:30:27 UTC

[jira] [Resolved] (SLING-2784) JcrResourceListener might deliver wrong remove events

     [ https://issues.apache.org/jira/browse/SLING-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2784.
-------------------------------------
    Resolution: Fixed

Due to the new resource provider api we can easily filter out the events. Added the check

> JcrResourceListener might deliver wrong remove events
> -----------------------------------------------------
>
>                 Key: SLING-2784
>                 URL: https://issues.apache.org/jira/browse/SLING-2784
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Resource 2.2.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Resource 2.6.0
>
>
> For add/change events, the resource listener checks whether this node is accessible via the resource api, however for remove events it is not. We should find a way to check whether the path is accessible using the resource api or shadowed by another resource provider. We have similar requirements for SLING-2783



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)