[
https://issues.apache.org/jira/browse/JCR-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315602#comment-17315602
]
Julian Reschke commented on JCR-4680:
-------------------------------------
[~angela]- changing primary types is a complex operation on it's own, so maybe
we want to consider this simpler case first :).
The proposed fix indeed makes the test pass, and doesn't seem to introduce any
regressions. However, I'm not familiar with this part of the code base so
wouldn't know whether this is the right approach.
Absent any other information I'm tempted to apply the patch now so it'll be
part of the upcoming (instable) release 2.11.6. Feedback appreciated.
> ConstraintViolationException in VersionManagerImplRestore when target node
> has a property definition unknown by the frozen node
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-4680
> URL: https://issues.apache.org/jira/browse/JCR-4680
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: versioning
> Affects Versions: 2.20.2
> Reporter: Eduardo Perez Garcia
> Priority: Major
> Attachments: JCR-4680-test.diff, VersionManagerImplRestore.patch
>
>
> If we attempt to restore a frozen node from the version history, but the
> target node has new property definitions (mixins), we get a
> ConstraintViolationException because the properties of the new node are
> processed after replacing its mixins with the mixins from the frozen node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
