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/24 14:50:58 UTC
[jira] [Commented] (JCR-4037) add includeSubtreeOnDelete flag to
JackrabbitEventFilter
[ https://issues.apache.org/jira/browse/JCR-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602215#comment-15602215 ]
Stefan Egli commented on JCR-4037:
----------------------------------
One use case for this is the following scenario: consider a listener that wants to be informed if a particular _property_ was deleted and what the old _value_ of that property was (eg when that property represents a reference to outside the repository). The support for getting the old value of the property is there: the info map contains the {{beforeValue}}. However, a listener is only informed if there is a direct filter match, ie if one of the ancestors is deleted, then you don't get an event. And that's what this ticket is about.
> 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)