You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2014/01/07 16:02:02 UTC

[jira] [Commented] (JCR-3711) RepositoryChecker versioning cleanup may leave repaired node in invalid type state

    [ https://issues.apache.org/jira/browse/JCR-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864310#comment-13864310 ] 

Marcel Reutegger commented on JCR-3711:
---------------------------------------

Patch looks good to me.

> RepositoryChecker versioning cleanup may leave repaired node in invalid type state
> ----------------------------------------------------------------------------------
>
>                 Key: JCR-3711
>                 URL: https://issues.apache.org/jira/browse/JCR-3711
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.4.5, 2.6.5, 2.7.3
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>         Attachments: JCR-3711.diff
>
>
> When detaching a version history, the repair code removes the mix:versionable mixin. However, it leaves the jcr:uuid property alone. If the effective node type of the repaired node does not allow a jcr:uuid property, the node will be in an inconsistent state.
> The existing tests in AutoFixCorruptNode did not uncover this because they use the default node type, nt:unstructured, in which case jcr:uuid falls back to a residual property.
> The suggested fix (in addition to test inprovements) is to add the mix:referenceable mixin.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)