[
https://issues.apache.org/jira/browse/JCR-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602110#comment-15602110
]
Stefan Egli commented on JCR-4045:
----------------------------------
[~cziegeler], could the same not be achieved by registering a separate,
dedicated listener that has {{isdeep}} set and listens on {{NODE_REMOVED}}?
> 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
>
> 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)
