jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (JCR-3765) JCR Event Info should contain NodeType
Date Tue, 29 Jul 2014 14:33:39 GMT

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

Michael Dürig commented on JCR-3765:

Applied the patch at http://svn.apache.org/r1614364

> 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

View raw message