You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2016/10/27 08:54:59 UTC

[jira] [Resolved] (JCR-4045) Improved support for node removals

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

Stefan Egli resolved JCR-4045.
------------------------------
    Resolution: Duplicate

Will be handled in OAK-5020

> Improved support for node removals
> ----------------------------------
>
>                 Key: JCR-4045
>                 URL: https://issues.apache.org/jira/browse/JCR-4045
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: core
>            Reporter: Carsten Ziegeler
>         Attachments: JCR-4045.patch
>
>
> If a listener is subscribed for removal events of a subtree, e.g. /a/b/c/d it gets removal events for everything in that three.
> However, if /a/b is removed, the listener is not informed at all, which makes the listener state inconsistent/invalid 
> I suggest to add a new flag to the JackrabbitEventFilter and if that is enabled the listener will get remove events of all the parent nodes - if the listener is interested in remove events of any kind.



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