Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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
Attachments
Issue Links
- is blocked by
-
-
- Closed
-