[
https://issues.apache.org/jira/browse/JCR-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated JCR-4048:
-----------------------------
Attachment: JCR-4048.patch
Attached [^JCR-4048] which suggests the introduction of a said new property to
the JackrabbitEventFilter:
* {{applyOnChild}}
If this property is set to true it would apply the filter for {{NODE_ADDED}},
{{NODE_REMOVED}} and {{NODE_MOVED}} to the child node, ie to the node that was
actually added/removed/moved and not only to the parent - given that the other
filter properties do match too that is.
> add applyOnChild property to JackrabbitEventFilter
> --------------------------------------------------
>
> Key: JCR-4048
> URL: https://issues.apache.org/jira/browse/JCR-4048
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: observation
> Affects Versions: 2.13.4
> Reporter: Stefan Egli
> Attachments: JCR-4048.patch
>
>
> There seems to be a rather frequent use case of observation around which
> would like to create a filter on a _child_ rather than on a _parent_:
> consider the case when you'd like to filter for the removal of a node that
> has a particular nodeType. This can't be achieved atm as the nodeType is
> applicable to the parent of the node that changes, not the node itself (ie
> child).
> Therefore suggesting the introduction of a flag similar to the following:
> {code}
> boolean applyOnChild;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
