[
https://issues.apache.org/jira/browse/JCR-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated JCR-2720:
--------------------------------
Summary: Changes from Session.move() to a top-level node aren't seen in
a second session (was: Changes from Session.move() aren't seen in a second
session)
Description:
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.
was:
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.
> 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
> 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.
