jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3635) Manually specified jcr:frozenUuid overwriting the one assigned by the VersionManager when versioning node
Date Thu, 01 Aug 2013 09:15:51 GMT

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

Jukka Zitting updated JCR-3635:
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6.4
                   2.4.5
                   2.2.14
           Status: Resolved  (was: Patch Available)

I committed the patch and the test case in http://svn.apache.org/r1509101. Thanks!

In the code I made a small adjustment to also ignore the jcr:frozenPrimaryType and jcr:frozenMixinTypes
properties if they for whatever reason exist in the node being checked in.

I also backported the fix to the 2.6, 2.4 and 2.2 maintenance branches, so it'll get shipped
along with the next patch releases.
                
> 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.2.14, 2.4.5, 2.6.4, 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

Mime
View raw message