jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3017) Version history recovery fails in case a version does not have a jcr:frozenNode
Date Wed, 05 Oct 2011 13:01:34 GMT

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

Julian Reschke updated JCR-3017:

    Attachment: JCR-3017.patch

introduce a new specific subclass of RTE for these situations and use it where appropriate
> Version history recovery fails in case a version does not have a jcr:frozenNode
> -------------------------------------------------------------------------------
>                 Key: JCR-3017
>                 URL: https://issues.apache.org/jira/browse/JCR-3017
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: versioning
>    Affects Versions: 2.2
>            Reporter: Honwai Wong
>            Assignee: Julian Reschke
>            Priority: Minor
>         Attachments: JCR-3017.patch
> With JCR-2551 in place, a version recovery mode has been introduced. Problem now is that
in case a version is encountered that misses a mandatory jcr:frozenNode, an InternalError
is thrown by o.a.j.c.version.InternalVersionHistoryImpl#createVersionInstance. Since o.a.j.c.RepositoryChecker#checkVersionHistory
only catches Exception, it fails to catch it properly which leads to a complete repository
> Throwing for example a RuntimeException instead fixes 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


View raw message