[JCR-1179] Event filtering by path not working as specified

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1, 1.3.3
• Fix Version/s: 1.4
• Component/s: jackrabbit-core, jackrabbit-spi, observation
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 18/Oct/07 10:33
• Updated: 15/Jan/08 23:27
• Resolved: 23/Oct/07 14:37

Description

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.

Issue Links

• is related to: JCR-1168 broken test in AddEventListener