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/08/18 22:01:18 UTC

[jira] Commented: (JCR-2720) Changes from Session.move() 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=12900005#action_12900005 ] 

Justin Edelson commented on JCR-2720:
-------------------------------------

tried a few things... none of which work

refresh(true) instead of refresh(false)
nodeExists() instead of itemExists()

session.getWorkspace().move() instead of session.move()



> Changes from Session.move() 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
>            Priority: Critical
>         Attachments: MoveTest.java
>
>
> I'll attach a test case, but basically...
> * Create two sessions
> * Create a node in the first session and save it.
> * Move the node in 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.