Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Fri, 21 Oct 2011 14:06:32 +0000 (UTC)
From: "Julian Reschke (Commented) (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <748664320.1016.1319205992125.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1299516169.13990.1318599371837.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (JCR-3115) Versioning fixup leaves persistence
 in a state where the node can't be made versionable again
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Julian Reschke commented on JCR-3115:
-------------------------------------

Modify checker to also inspect "candidate" version histories (trunk: 1187344, 2.2: 1187345). Test case (trunk only): 1187354.
                
> Versioning fixup leaves persistence in a state where the node can't be made versionable again
> ---------------------------------------------------------------------------------------------
>
>                 Key: JCR-3115
>                 URL: https://issues.apache.org/jira/browse/JCR-3115
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, versioning
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 2.2.10, 2.3.2
>
>         Attachments: AutoFixCorruptNode.java, JCR-3115.patch, JCR-3115.patch, JCR-3115.patch, JCR-3115.patch
>
>
> Jackrabbit's version recovery mode (org.apache.jackrabbit.version.recovery system property) disconnects all version histories that expose problems that manifest in unexpected exceptions being thrown. "disconnects" means removing the properties defined for mix:versionable and removing the mixin type. The actual versioning related nodes remain in place.
> The problem: when re-adding mix:versionable, ItemSaveOperation.initVersionHistories tries to create the new version history in the same location (the path being derived from the versionable node's identifier), and consequently fails because of the broken underlying storage.
> (attaching a work-in-progress test case that illustrates the problem)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira