You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2016/11/01 11:21:58 UTC
[jira] [Commented] (OAK-5022) add includeSubtreeOnDelete flag to
OakEventFilter
[ https://issues.apache.org/jira/browse/OAK-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15625169#comment-15625169 ]
Stefan Egli commented on OAK-5022:
----------------------------------
[test case for beforeValue added|http://svn.apache.org/viewvc?rev=1767476&view=rev]
> add includeSubtreeOnDelete flag to OakEventFilter
> -------------------------------------------------
>
> Key: OAK-5022
> URL: https://issues.apache.org/jira/browse/OAK-5022
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Affects Versions: 1.5.12
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Fix For: 1.5.13
>
>
> (Originally reported as JCR-4037, but moved to Oak as a result of introducing the OakEventFilter in OAK-5013. From the original description: )
> 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 includeSubtreeOnRemove;
> {code}
> (Open for any better name of course)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)