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] Updated: (JCR-2720) Changes from Session.move() to a top-level node aren't seen in a second session
Date Fri, 17 Sep 2010 10:12:33 GMT

     [ https://issues.apache.org/jira/browse/JCR-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-2720:
-------------------------------

    Attachment: JCR-2720.patch

I believe this is due to the special way we handle the root path in the CachingHierarchyManager.
The attached patch makes the nodeModified() event handler take that special case into account
so that also changes to the paths of top-level nodes are correctly reflected in the path cache.

> Changes from Session.move() to a top-level node aren't seen in a second session
> -------------------------------------------------------------------------------
>
>                 Key: JCR-2720
>                 URL: https://issues.apache.org/jira/browse/JCR-2720
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>            Reporter: Justin Edelson
>            Assignee: Stefan Guggisberg
>         Attachments: JCR-2720-test.patch, JCR-2720.patch, MoveTest.java
>
>
> I'll attach a test case, but basically...
> * Create two sessions
> * Create a top-level node in the first session and save it.
> * Move the top-level node using the first session
> * In the second session, try itemExists() for the path of the node. It returns true when
it should be false.

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


Mime
View raw message