[jira] Assigned: (JCR-155) renaming a node with Session.move() or Workspace.move() is not visible from other concurrent sessions

["Stefan Guggisberg (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/JCR-155?page=all ]

Stefan Guggisberg reassigned JCR-155:
-------------------------------------

    Assign To: Dominique Pfister  (was: Stefan Guggisberg)

CachingHierarchyManager instance of other session is not notified about the change and therefore does not flush the previously cached and now invalid path from its cache.

> renaming a node with Session.move() or Workspace.move() is not visible from other concurrent sessions
> -----------------------------------------------------------------------------------------------------
>
>          Key: JCR-155
>          URL: http://issues.apache.org/jira/browse/JCR-155
>      Project: Jackrabbit
>         Type: Bug
>   Components: core
>  Environment: SVN rev.  202548
>     Reporter: Stefan Guggisberg
>     Assignee: Dominique Pfister
>      Fix For: 1.0

>
> this is a CachingHierarchyManager issue.
> to reproduce:
> Node n1 = session1.getRootNode().getNode("foo");
> String path = n1.getPath();   // returns "/foo"
> Node n2 = session2.getRootNode().getNode("foo");
> path = n2.getPath();   // returns "/foo"
> session1.move("/foo", "/bar");
> session1.save();
> path = n1.getPath();   // returns "/bar"
> path = n2.getPath();   // should return "/bar" but still returns "/foo"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira