[ 
https://issues.apache.org/jira/browse/JCR-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725286#comment-13725286
 ] 

Florin Iordache commented on JCR-3635:
--------------------------------------

[~anchela]
I've only specified "manually" (and also test-cased this) for the sake of 
showing that this is possible.
The same would happen if at some point someone decides to automatically copy 
all the properties of a node's version to another node without skipping the 
frozenUuid.
This should be automatically managed during the version creation, without the 
possibility to overwrite by mistake if a such property would exist on the 
source node.
                
> 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
>            Assignee: Jukka Zitting
>             Fix For: 2.7.1
>
>         Attachments: CopyFrozenUuidTest.java, JCR-3635.patch
>
>
> 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

Reply via email to