[
https://issues.apache.org/jira/browse/JCR-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529079#comment-15529079
]
Stefan Egli commented on JCR-4035:
----------------------------------
So, assuming we add something like below, should we add a note that this is
only optionally supported (ie not in JCR 2, only in Oak)?
{code}
/**
* Sets the <code>parentTreeNodeTypeNames</code> parameter of the filter.
* If left unset, this parameter defaults to <code>null</code>.
* Note that support for this is optional and depends on implementation.
*
* @param parentTreeNodeTypeNames a <code>String</code> array.
* @return This EventFilter object with the
<code>parentTreeNodeTypeNames</code> parameter set.
*/
public JackrabbitEventFilter setParentTreeNodeTypes(String[]
parentTreeNodeTypeNames) {
...
}
{code}
> consider supporting parentNodeTypes filtering in observation
> ------------------------------------------------------------
>
> Key: JCR-4035
> URL: https://issues.apache.org/jira/browse/JCR-4035
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: observation
> Affects Versions: 2.13.3
> Reporter: Stefan Egli
>
> For some types of applications it might be useful to specify a nodetype that
> any parent (ie including grand/grand-grand/etc parent) must have in order to
> receive an event. The alternative (if this doesn't exist, as today) is to
> receive all events and do the filtering in the listener - which is less
> efficient.
> This is also related to JCR-4016 / JCR-4017
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
