[
https://issues.apache.org/jira/browse/OAK-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705939#comment-13705939
]
Jukka Zitting commented on OAK-898:
-----------------------------------
Looking at the test case, a {{node1.getSession().refresh()}} call seems to be
missing. Note that with Oak sessions are based on snapshots of the repository
state, so a refresh, either explicit or implicit (triggered for example by the
auto-refresh feature), is needed for changes from another session to become
visible. Also, we currently only track moves within a single session, so in
this case {{node1}} would actually become invalid after the refresh.
> Session#move with a fresh session doesn't work properly
> -------------------------------------------------------
>
> Key: OAK-898
> URL: https://issues.apache.org/jira/browse/OAK-898
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Alex Parvulescu
>
> The scenario is as follows: create a node, then try to move it using a new
> session.
> Will attach a test case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
