[
https://issues.apache.org/jira/browse/JCR-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303262#comment-17303262
]
Julian Reschke edited comment on JCR-4680 at 3/17/21, 10:49 AM:
----------------------------------------------------------------
Interesting problem. Did you check whether the specification has an opinion
about this case? (We may also want to check what Oak does here...).
IIUC, the idea is that the restore operation should also remove the added mixin
type, and thus succeed? Would be good to have a test for that in the TCK
(jackrabbir-jcr-tests), so that it would also be used for other implementations
of the JCR API.
was (Author: reschke):
Interesting problem. Did you check whether the specification has an opinion
about this case? (We may also want to check what Oak does here...).
> 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: 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)
