You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2008/10/10 12:21:44 UTC
[jira] Created: (JCR-1799) JCR2SPI: updating events swallowed
(CacheBehavior.OBSERVATION)
JCR2SPI: updating events swallowed (CacheBehavior.OBSERVATION)
--------------------------------------------------------------
Key: JCR-1799
URL: https://issues.apache.org/jira/browse/JCR-1799
Project: Jackrabbit
Issue Type: Bug
Components: jackrabbit-jcr2spi
Reporter: angela
Assignee: angela
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1799) JCR2SPI: updating events swallowed
(CacheBehavior.OBSERVATION)
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-1799.
-------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
> JCR2SPI: updating events swallowed (CacheBehavior.OBSERVATION)
> --------------------------------------------------------------
>
> Key: JCR-1799
> URL: https://issues.apache.org/jira/browse/JCR-1799
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-jcr2spi
> Reporter: angela
> Assignee: angela
> Fix For: 1.5.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.