[ https://issues.apache.org/jira/browse/JCR-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315470#comment-17315470 ]
Angela Schreiber commented on JCR-4680: --------------------------------------- [~reschke], yes.... i even suspect that this is not limited to mixins but the same applies if the primary type had changed. and in addition: it might even affect child nodes not just properties. > 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)