[
https://issues.apache.org/jira/browse/JCR-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated JCR-4046:
-----------------------------
Attachment: JCR-4046.v2.patch
bq. What's perhaps less straight-forward is to have an event be reported on
another path than where it happend - aka 'moving an event'. That would have to
be explicit, additional code that the filters can't handle.
I've spawned this 'move' aka 'aggregation' part into OAK-5011 and added a patch
suggesting how this could be achieved.
Based on OAK-5011 we could then, similarly as suggested in JCR-4044, implement
this aggregation feature request in the oak-jcr level, independent of
jackrabbit: attached [^JCR-4046.v2.patch] which illustrates this (this is based
on the patch attached to OAK-5011)
> 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
> Attachments: JCR-4046.patch, JCR-4046.v2.patch
>
>
> 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)
