You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/05/10 23:58:23 UTC

[jira] [Resolved] (SLING-3551) Content sync does not propagate mixin types

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

Robert Munteanu resolved SLING-3551.
------------------------------------

    Resolution: Fixed

> Content sync does not propagate mixin types
> -------------------------------------------
>
>                 Key: SLING-3551
>                 URL: https://issues.apache.org/jira/browse/SLING-3551
>             Project: Sling
>          Issue Type: Bug
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.0.0
>
>
> Assume that we have a full coverage aggregate as follows:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:vlt="http://www.day.com/jcr/vault/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
>     jcr:mixinTypes="[mix:language]"
>     jcr:primaryType="nt:folder"
>     jcr:language="en">
>     <message
>         jcr:primaryType="sling:MessageEntry"
>         sling:key="message"
>         sling:value="Message">
>     </message>
>     <error
>         jcr:primaryType="sling:MessageEntry"
>         sling:key="error"
>         sling:value="Error">
>     </error>
>     <warning
>         jcr:primaryType="sling:MessageEntry"
>         sling:key="warning"
>         sling:value="Warning">
>     </warning>
> </jcr:root>
> {code}
> When synced to the repo this will fail with the following message
> {quote}!MESSAGE Failed publishing JcrResult[ success:false, exception: org.apache.sling.ide.transport.RepositoryException - javax.jcr.nodetype.ConstraintViolationException: no matching property definition found for {http://www.jcp.org/jcr/1.0}language]{quote}
> The reason is that the jcr:mixinTypes property is protected, and therefore skipped. We need to handle this explicitly.



--
This message was sent by Atlassian JIRA
(v6.2#6252)