[ 
https://issues.apache.org/jira/browse/SLING-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15580003#comment-15580003
 ] 

Carsten Ziegeler commented on SLING-6163:
-----------------------------------------

As a first improvement, we only read the parent node on change events - for 
node added and removed we don't need to do this, as the jcr:content node is 
mandatory, so if it is added the above file node is added as well, same for 
remove

> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to