[WIP] child version cascade tests (fails) #85
Conversation
| @@ -26,6 +26,17 @@ | |||
| <sv:property sv:name="foo" sv:type="String"> | |||
| <sv:value>something</sv:value> | |||
| </sv:property> | |||
| <sv:node sv:name="version_child"> | |||
| <sv:property sv:name="jcr:primaryType" sv:type="Name"> | |||
| <sv:value>phpcr:versionCascade</sv:value> | |||
There was a problem hiding this comment.
The child can probably can be nt:unstructured rather than phpcr:versionCascade...
|
ftr fazy mailed to the jackrabbit mailinglist, but got no replies. he since did the workspace clone method which was much easier to achieve and helps with draft and production already. i'd suggest we leave this open in case somebody ever wants to hunt the issues down, then he has some tests to start with... |
|
Here's my posting on the Jackrabbit list: I hope to also use versioning in due course, i.e. a workflow where the all the changes, version history, revert to earlier version take place in a "preview" workspace, and a publish action causes these changes to be updated to the "published" workspace. So any insight on the above would be useful. |
|
just a note (i guess you already saw that, but for others): when |
Tests to demonstrate how I believe version cascade should work.
For now, I've added a child node to the 'versioned' node in the fixtures and added extra test cases to 15_Versioning/VersionTest.php. However, if it's better I'll be happy to move these tests to a separate test class (and with separate fixtures if needed).
Also, does the CND type look correct?