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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1, 2.4.1
• Fix Version/s: 2.5.1
• Component/s: jackrabbit-jcr-tests, JCR 2.0
• Assignee: Julian Reschke
• Reporter: Brian Carothers
• Created: 20/Jun/10 15:43
• Updated: 06/Aug/12 14:16
• Resolved: 13/Jul/12 12:34

Description

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."

Issue Links

• is required by: JCR-3326 missing test configuration for org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreNameJcr2()