[jira] Created: (JCR-2666) JCR TCK Test for Restoring Version Tests That Versionable Child Is also Restored, contrary to JCR 2.0 specification

["Brian Carothers (JIRA)" <ji...@apache.org>]

JCR TCK Test for Restoring Version Tests That Versionable Child Is also Restored, contrary to JCR 2.0 specification
-------------------------------------------------------------------------------------------------------------------

                 Key: JCR-2666
                 URL: https://issues.apache.org/jira/browse/JCR-2666
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-jcr-tests, JCR 2.0
    Affects Versions: 2.1.0
            Reporter: Brian Carothers


The test case testRestoreNameJcr2 in o.a.j.test.version.RestoreTest, ends by validating that restoring a versionable parent also restores its versionable child.  This was the correct behavior in JCR 1.0, but was changed in JCR 21].  The testRestoreName method in the same class correctly notes this and changed the behavior for JCR 2.

This can be corrected by replacing the last 3 lines of testRestoreNameJcr2 with something analogous to the last 5 lines of testRestoreName.

Thanks!

[1] - JCR2 specification, section 15.7.5 - "If the workspace currently has an already existing node corresponding to C's version history and the removeExisting flag of the restore is set to true, then that instance of C becomes the child of the restored N."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.