[jira] [Commented] (JCR-4035) consider supporting parentNodeTypes filtering in observation
[
https://issues.apache.org/jira/browse/JCR-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 parentTreeNodeTypeNames parameter of the filter.
* If left unset, this parameter defaults to null.
* Note that support for this is optional and depends on implementation.
*
* @param parentTreeNodeTypeNames a String array.
* @return This EventFilter object with the
parentTreeNodeTypeNames 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)
[jira] [Commented] (JCR-4035) consider supporting parentNodeTypes filtering in observation
[ https://issues.apache.org/jira/browse/JCR-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528991#comment-15528991 ] Michael Dürig commented on JCR-4035: Direct parent only currently, yes. > 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 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)
[jira] [Commented] (JCR-4035) consider supporting parentNodeTypes filtering in observation
[ https://issues.apache.org/jira/browse/JCR-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528987#comment-15528987 ] Stefan Egli commented on JCR-4035: -- I was referring to the entire parent/grandparent/grand-grandparent etc hierarchy - afaics currently only the direct parent's node type counts? > 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 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)
[jira] [Commented] (JCR-4035) consider supporting parentNodeTypes filtering in observation
[
https://issues.apache.org/jira/browse/JCR-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528970#comment-15528970
]
Michael Dürig commented on JCR-4035:
bq. nodetype that any parent must have
This is how node type filtering is done. Filtering is per specification done on
the associated parent node. See also the Javadoc on
{{ObservationManager#addEventListener}}.
> 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 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)
