jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (OAK-1661) JCR Event Info should contain NodeType for Events Type Node-Deleted
Date Wed, 02 Apr 2014 15:01:31 GMT

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

Michael Dürig edited comment on OAK-1661 at 4/2/14 2:59 PM:
------------------------------------------------------------

Fixed at http://svn.apache.org/r1584053

{{Event.getInfo()}} contains the primary and mixin node types of the added/removed node in
the case of {{Event.NODE_ADDED}} and {{Event.NODE_REMOVED}}. The key {{jcr:primaryType}} maps
to the primary type and the key {{jcr:mixinTypes}} maps to an array containing the mixin types.


was (Author: mduerig):
Fixed at http://svn.apache.org/r1584053

> JCR Event Info should contain NodeType for Events Type Node-Deleted
> -------------------------------------------------------------------
>
>                 Key: OAK-1661
>                 URL: https://issues.apache.org/jira/browse/OAK-1661
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>    Affects Versions: 0.19
>            Reporter: Christan Keller
>            Assignee: Michael Dürig
>            Priority: Blocker
>             Fix For: 0.20
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message