You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2010/09/14 18:58:32 UTC
[jira] Commented: (JCR-2720) Changes from Session.move() to a
top-level node aren't seen in a second session
[ https://issues.apache.org/jira/browse/JCR-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909327#action_12909327 ]
Justin Edelson commented on JCR-2720:
-------------------------------------
Stefan-
Sorry I missed your response to this issue. I can reproduce this against trunk (with or without the refresh call)
I'll attach a patch with the test case.
Justin
> 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: 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.