[
https://issues.apache.org/jira/browse/SLING-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15581543#comment-15581543
]
Stefan Egli commented on SLING-6163:
------------------------------------
At the moment this is all oak internal and hasn't been exposed yet, so we need
to define this.
Re the example
bq. if a jcr:content node is modified
IIUC you're referring to a change of a property of a jcr:content node, right?
As that would not result in the nodeType of the parent of jcr:content to be
reported. If properties of jcr:content are modified then only the jcr:content
node is reported in OAK-4907 (name, nodeType, path of it)
> Improve observation of files in JCR
> -----------------------------------
>
> Key: SLING-6163
> URL: https://issues.apache.org/jira/browse/SLING-6163
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.0
>
>
> Currently, if a jcr:content node is modified, and an observation event is
> sent out, the jcr listener reads the parent node to find out if this
> jcr:content is a sub node of a file. If so, it reports a change on the file
> node.
> This is required for all listeners interested in changes in files, as they
> usually listen for a file node change, but not for the sub node /jcr:content
> - which doesn't exist with other resource providers anyway
> The problem is that this read is done for every change of a jcr:content node,
> regardless whether this is a file. And if several props change on such a
> node, it is read over and over again
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
