Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 593E811A20 for ; Tue, 29 Jul 2014 12:49:39 +0000 (UTC) Received: (qmail 66250 invoked by uid 500); 29 Jul 2014 12:49:39 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 66174 invoked by uid 500); 29 Jul 2014 12:49:39 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 66156 invoked by uid 99); 29 Jul 2014 12:49:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jul 2014 12:49:39 +0000 Date: Tue, 29 Jul 2014 12:49:38 +0000 (UTC) From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (JCR-3765) JCR Event Info should contain NodeType MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCR-3765?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Michael D=C3=BCrig reassigned JCR-3765: ---------------------------------- Assignee: Michael D=C3=BCrig > 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=C3=BCrig > Assignee: Michael D=C3=BCrig > Priority: Minor > 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 processi= ng 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 event= s. We should consider adding this for all event types however. Even propert= y events would contain node type of the node the property is associated wit= h (parent). > An implication of this is however that we also need to adapt the TCK as t= his will cause org.apache.jackrabbit.test.api.observation.GetInfoTest to fa= il, which expects the info map to be generally empty. -- This message was sent by Atlassian JIRA (v6.2#6252)