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 "angela (JIRA)" <ji...@apache.org> on 2013/07/18 14:46:48 UTC
[jira] [Comment Edited] (OAK-918) Copying nodes does not create
independant version histories
[ https://issues.apache.org/jira/browse/OAK-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712277#comment-13712277 ]
angela edited comment on OAK-918 at 7/18/13 12:45 PM:
------------------------------------------------------
JSR 283 states the following with respect to copy of versionable nodes:
3.13.5.6 Copied From
When a full versionable node is copied to a new location and the repository preserves the mix:versionable mixin (see §10.7 Copying Nodes), the copy gets a new version history and that history records the base version of the node from which the copy was created. This information, known as the node's lineage, is recorded in the jcr:copiedFrom WEAKREFERENCE property of nt:versionHistory (see §15.1.4 Copying Versionable Nodes and Version Lineage).
and later on:
15.1.4 Copying Versionable Nodes and Version Lineage
Under both simple and full versioning, when an existing versionable node N is copied to a new location either in the same workspace or another, and the repository preserves the versionable mixin (see §10.7.4 Dropping Mixins on Copy):
• A copy of N, call it M, is created, as usual.
• A new, empty, version history for M, call it HM, is also created. Under full versioning:
• The properties jcr:versionHistory, jcr:baseVersion and jcr:predecessors of M are not copied from N but are initialized as usual.
• The jcr:copiedFrom property of HM is set to point to the base version of N. 15.1.4.1 Version Lineage
The jcr:copiedFrom property allows an application to determine the lineage of a version across version histories that were produced by copying a versionable node to a new location.
this is currently not implemented with the result that the copied tree shares all version information with the original nodes.
was (Author: anchela):
JSR 283 states the following with respect to copy of versionable nodes:
3.13.5.6 Copied From
When a full versionable node is copied to a new location and the repository preserves the mix:versionable mixin (see §10.7 Copying Nodes), the copy gets a new version history and that history records the base version of the node from which the copy was created. This information, known as the node's lineage, is recorded in the jcr:copiedFrom WEAKREFERENCE property of nt:versionHistory (see §15.1.4 Copying Versionable Nodes and Version Lineage).
this is currently not implemented with the result that the copied tree shares all version information with the original nodes.
> Copying nodes does not create independant version histories
> -----------------------------------------------------------
>
> Key: OAK-918
> URL: https://issues.apache.org/jira/browse/OAK-918
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Reporter: angela
>
--
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