You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2016/10/20 14:50:59 UTC

[jira] [Commented] (JCR-4046) Improve observation of files

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

Stefan Egli commented on JCR-4046:
----------------------------------

Note that this is a specialization (restricted version) of JCR-4035. Perhaps it's good enough to just allow having the filters be applied to grand-parent and not further up the hierarchy.

> Improve observation of files
> ----------------------------
>
>                 Key: JCR-4046
>                 URL: https://issues.apache.org/jira/browse/JCR-4046
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: core
>            Reporter: Carsten Ziegeler
>
> A file in JCR is represented by at least two nodes, the nt:file node and a child node named jcr:content holding the contents of the file (and metadata).
> This has the consequence that if the contents of a file changes, a change event of the jcr:content node is reported - but not of the nt:file node.
> This makes creating listeners listening for changes in files complicated, as you can't use the file name to filter  - especially with glob patterns (see JCR-4044) this becomes troublesome.
> In addition, whenever you get a change for a jcr:content node, you have to check if the parent is a nt:file node and decide based on the result.
> It would be great to have a flag on the JackrabbitEventFilter to enable smarter reporting just for nt:files: if a property on jcr:content is changed, a change to the nt:file node is reported.
> See also SLING-6163 and OAK-4940



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