You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2019/12/18 12:42:01 UTC
[jira] [Closed] (JCR-3765) JCR Event Info should contain NodeType
[ https://issues.apache.org/jira/browse/JCR-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke closed JCR-3765.
-------------------------------
> JCR Event Info should contain NodeType
> --------------------------------------
>
> Key: JCR-3765
> URL: https://issues.apache.org/jira/browse/JCR-3765
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Priority: Minor
> Labels: observation
> Attachments: JCR-3765.patch
>
>
> This issue is about back porting the features introduced in Oak with OAK-1661 and OAK-1669:
> Code developped for Jackrabbit's Observation often struggle with processing events for deleted Nodes. Processing like for aggregation may depend on the type of the deleted Node. The solution to take a Nodetype filter could be prevented or some reasons.
> Adding the node-type to the Event's Info object would help in this cases. OAK-1661 added node type information for NODE_ADDED and NODE_REMOVED events. We should consider adding this for all event types however. Even property events would contain node type of the node the property is associated with (parent).
> An implication of this is however that we also need to adapt the TCK as this will cause org.apache.jackrabbit.test.api.observation.GetInfoTest to fail, which expects the info map to be generally empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)