[JCR-1799] JCR2SPI: updating events swallowed (CacheBehavior.OBSERVATION)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5
• Component/s: jackrabbit-jcr2spi
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 10/Oct/08 10:20
• Updated: 08/Dec/08 11:09
• Resolved: 14/Oct/08 07:45

Description

with CacheBehavior.OBSERVATION the hierarchy held within jcr2spi is updated based on events.

if Session-A persistently adds a mix:referenceable to a Node that is already loaded in Session-B, the latter will not be informed about this change.

Reason: upon processing the SPI Event (-> HierarchyEventListener#onEvent) the parent is retrieved by the Event ItemId, which in the former case contains a uniqueID part, which is not known yet to the listening Session-B.
Consequently the NodeEntry affected by the event is not updated.

Possible fix: If looking up the parent entry of the event doesn't succeed, a 2nd lookup using the Event path should be performed.