jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-2340) CacheBehaviour Observation broken
Date Fri, 02 Oct 2009 12:25:23 GMT

    [ https://issues.apache.org/jira/browse/JCR-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761562#action_12761562

Michael Dürig commented on JCR-2340:

The 3rd point from my previous comment is invalid. I was mixing up hierarchies from different

For the first point I think the JavaDoc is out of sync and the actual implementation is tight.

> CacheBehaviour Observation broken
> ---------------------------------
>                 Key: JCR-2340
>                 URL: https://issues.apache.org/jira/browse/JCR-2340
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 2.0.0
>            Reporter: Michael Dürig
> While trying to fix JCR-2293 I discovered that CacheBehaviour Observation is broken:
> - HierarchyEventListener.onEvent ignores local event (despite the comment saying otherwise).
Not sure which way it should be. However with local events being ignored, JCR-2293 will most
probably also occur with CacheBehaviour Observation. 
> - NodeEntryImpl.refresh(Event) does not set its child node entries to incomplete when
a node/property was added.
> - After tentatively fixing above issues, I discovered that NodeEntryImpl.refresh(Event)
and my own event listener operate on different NodeEntryImpl and ChildNodeEntryImpl instances.
That is, even though I set childNodeEntries.complete to false in NodeEntryImpl.refresh(Event),
when my own event listener retrieves that node (entry), it gets a different instance which
has childNodeEntries.complete still set to true.

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

View raw message