[jira] [Updated] (JCR-3635) Manually specified jcr:frozenUuid overwriting the one assigned by the VersionManager when versioning node

["Florin Iordache (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florin Iordache updated JCR-3635:
---------------------------------

    Attachment: CopyFrozenUuidTest.java

Attached test case for this issue:
* creating node {{firstNode}} and version
* read the frozenUuid of the {{firstNode}} version and assigned to a second node {{secondNode}}

--> Result: when versioning the {{secondNode}} the resulting frozenUuid is the same as the version of {{firstNode}}
--> Expected result: the two frozenUuid's should be different
                
> Manually specified jcr:frozenUuid overwriting the one assigned by the VersionManager when versioning node
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-3635
>                 URL: https://issues.apache.org/jira/browse/JCR-3635
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: versioning
>    Affects Versions: 2.7
>            Reporter: Florin Iordache
>         Attachments: CopyFrozenUuidTest.java
>
>
> Let's assume we have node N with a manually assigned jcr:frozenUuid property (e.g. taken from an existing frozenNode version of another node).
> When creating versions of node N, the manually assigned frozenUuid property will overwrite the frozenUuid automatically created by the VersionManager in the versioning process because the jcr:frozenUuid property is not skipped when copying the existing properties from the versioned node to the frozen node in the version subtree.
> This can potentially cause issues whenever the jcr:frozenUuid is used in the future, since it would basically point to a different versioned node.

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