[
https://issues.apache.org/jira/browse/JCR-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602696#comment-15602696
]
Chetan Mehrotra commented on JCR-4048:
--------------------------------------
+1. I have also got bitten by current behaviour which to me was not intuitive!
bq. applyOnChild
child again is bit misleading. May be {{applyOnSelf}} or {{forCurrentNode}}.
And may be prefer no arg variant for boolean property i.e. method invocation
itself is indication to make it true
{code}
+ public JackrabbitEventFilter applyOnCurrentNode() {
+ this.applyOnChild = true;
+ return this;
+ }
{code}
Not able to come up with good name though ...
> 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)
