You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/02/05 16:09:12 UTC

[jira] [Commented] (OAK-606) Node becomes invalid after Session#move()

    [ https://issues.apache.org/jira/browse/OAK-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571366#comment-13571366 ] 

Michael Dürig commented on OAK-606:
-----------------------------------

This change in behaviour was introduced in OAK-391 as discussed on the list [1] and as documented by {{CompatibilityIssuesTest}} [2].

[1] http://markmail.org/message/b6dcyae362akyogd
[2] https://fisheye6.atlassian.com/viewrep/jackrabbit/oak/trunk/oak-jcr/src/test/java/org/apache/jackrabbit/oak/jcr/CompatibilityIssuesTest.java?r1=1374270&r2=1404646 
                
> 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
>
> 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