[
https://issues.apache.org/jira/browse/JCR-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601812#comment-15601812
]
Stefan Egli edited comment on JCR-4037 at 10/24/16 2:14 PM:
------------------------------------------------------------
-JCR-4045 is an inverse approach which suggests to introduce
{{includeAncestors}} (which is kind of the opposite of {{isDeep}}) which sounds
a better way of solving this issue, hence closing this one.-
EDIT: Reopend JCR-4037 as the two aren't really that equal and it's not given
that we do JCR-4045 at this stage
was (Author: egli):
JCR-4045 is an inverse approach which suggests to introduce
{{includeAncestors}} (which is kind of the opposite of {{isDeep}}) which sounds
a better way of solving this issue, hence closing this one.
> add includeSubtreeOnDelete flag to JackrabbitEventFilter
> --------------------------------------------------------
>
> Key: JCR-4037
> URL: https://issues.apache.org/jira/browse/JCR-4037
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: observation
> Affects Versions: 2.13.3
> Reporter: Stefan Egli
>
> In some cases of observation it would be useful to receive events of child
> node or properties of a parent/grandparent that was deleted. Currently (in
> Oak at least) one only receives a deleted event for the node that was deleted
> and none of the children.
> Suggesting to (re)introduce a flag, eg as follows to the
> JackrabbitEventFilter:
> {code}
> boolean includeSubtreeOnDelete;
> {code}
> (Open for any better name of course)
> /cc [~mduerig], [~mreutegg]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
