[
https://issues.apache.org/jira/browse/JCR-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782426#action_12782426
]
Stefan Guggisberg commented on JCR-2408:
----------------------------------------
you should always be able to remove a mixin which has been previously added.
how conflicts are resolved is an implementation choice.
when removing a mixin M declaring a property P, the current implementation
first tries
migrate P to a definition declared by the resulting effective node type. if
this fails,
the property is removed.
> Mixin removal exception
> -----------------------
>
> Key: JCR-2408
> URL: https://issues.apache.org/jira/browse/JCR-2408
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.0-beta1
> Reporter: Alexandre Capt
>
> When trying to remove a mixin from a non nt:unstructured node (in my case
> nt:resource), you get the following exception:
> Unable to alter mixin types: javax.jcr.nodetype.ConstraintViolationException:
> no matching property definition found for
> {http://www.day.com/jcr/cq/1.0}lastRolledout
> lastRolledout property is defined by the mixin cq:LiveRelationship that I am
> trying to remove.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
