jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2720) Changes from Session.move() to a top-level node aren't seen in a second session
Date Mon, 23 Aug 2010 16:28:17 GMT

    [ https://issues.apache.org/jira/browse/JCR-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901467#action_12901467
] 

Stefan Guggisberg commented on JCR-2720:
----------------------------------------

i tried to reproduce the said behavior on jackrabbit trunk with the provided test case, however
i failed (i.e. the test case succeeded as expected).
all i had to change was the package statement.

btw: you don't need to call session2.refresh() when using jackrabbit-core, since changes saved
by one session should be visible to other sessions instantly.

could you please try to reproduce the issue on jackrabbit trunk?


> 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
>            Priority: Critical
>         Attachments: 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