jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5020) Improved support for node removals
Date Wed, 02 Nov 2016 05:35:58 GMT

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

Carsten Ziegeler commented on OAK-5020:
---------------------------------------

[~egli] The javadoc mentions "!deep NODE_REMOVED registrations" - does this mean that if a
listener is registering with the deep flag enabled, this doesn't apply?

> Improved support for node removals
> ----------------------------------
>
>                 Key: OAK-5020
>                 URL: https://issues.apache.org/jira/browse/OAK-5020
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>    Affects Versions: 1.5.12
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.5.13
>
>
> (Originally reported as JCR-4045, but moved to Oak as a result of introducing the OakEventFilter
in OAK-5013. From the original description: )
> If a listener is subscribed for removal events of a subtree, e.g. /a/b/c/d it gets removal
events for everything in that three.
> However, if /a/b is removed, the listener is not informed at all, which makes the listener
state inconsistent/invalid
> I suggest to add a new flag to the JackrabbitEventFilter and if that is enabled the listener
will get remove events of all the parent nodes - if the listener is interested in remove events
of any kind.
> /cc [~cziegeler]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message