[
https://issues.apache.org/jira/browse/OAK-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578333#comment-13578333
]
Michael Dürig commented on OAK-606:
-----------------------------------
At revision 1446141 I implemented Jukka's proposal from above. This gives us a
sound basis for further refinements.
Currently a node becomes invalid when it is removed or moved. Any further
access to that node results in an {{InvalidItemStateException}}. When a new
item is added at the same location later, the node becomes valid again
'pointing' to that new item. See {{MoveRemoveTest}} and {{MoveTest}} for the
fine print.
# If we want to change the behaviour for moves such that node instances stay
valid when its underlying item is moved (i.e. point to the moved item), we need
to track transient moves operations [as mentioned earlier |
https://issues.apache.org/jira/browse/OAK-606?focusedCommentId=13572350&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13572350].
# If we want to change the behaviour such that removed nodes stay invalid even
though a new item has been added an the same location, we need to implement the
same tracking logic like for moves operation also for remove operations.
> Node becomes invalid after Session#move()
> -----------------------------------------
>
> Key: OAK-606
> URL: https://issues.apache.org/jira/browse/OAK-606
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
> Assignee: Michael Dürig
> Attachments: OAK-606.patch
>
>
> moving or renaming an existing (saved) node renders that node instance
> invalid and any access on that node instance will throw IllegalStateException.
--
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
