jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1179) Event filtering by path not working as specified
Date Tue, 23 Oct 2007 11:56:52 GMT

    [ https://issues.apache.org/jira/browse/JCR-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536971

Jukka Zitting commented on JCR-1179:


I'll mention the backwards compatibility issue in the 1.4 release notes. If someone relies
on the current behaviour, they should delay the 1.4 upgrade until the client code is fixed.

> Event filtering by path not working as specified
> ------------------------------------------------
>                 Key: JCR-1179
>                 URL: https://issues.apache.org/jira/browse/JCR-1179
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: observation
>            Reporter: Julian Reschke
>         Attachments: JCR-1179.patch
> When filtering node events by path, the event filter doesn't compare using the "associated
parent path", see JSR-170, 8.3.3:
> "The set of events can be filtered by specifying restrictions based on characteristics
of the associated parent node of the event. The associated parent node of an event is the
parent node of the item at (or formerly at) the path returned by Event.getPath. The following
restrictions are available:
> • absPath, isDeep: Only events whose associated parent node is at absPath (or within
its subtree, if isDeep is true) will be received. It is permissible to register a listener
for a path where no node currently exists."
> (for property events, filtering is correct)
> To fix this, the special handling of node events in EventFilter.blocks() simply needs
to be removed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message