[ https://issues.apache.org/jira/browse/JCR-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603082#comment-15603082 ]
Michael Dürig commented on JCR-4048: ------------------------------------ >From the Javadoc: {quote} * @param applyOnChild a <code>boolean</code> that when set to true * indicates that the filter parameters (ie eventTypes, paths, isDeep, * nodeTypes, identifiers) should not only be applied to the parent * (which is the default) but also on the child (which only applies * for node events, not property events). * @return This EventFilter object with the <code>applyOnChild</code> parameter set. {quote} "not only, but also": is this intentional? Why? Shouldn't it be "instead"? > 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)