You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org> on 2011/11/16 19:20:52 UTC
[jira] [Updated] (JCR-3121)
InternalVersionManagerBase.getVersionHistoryOfNode should throw
InconsistentVersioningState when it encounters a runtime exception
[ https://issues.apache.org/jira/browse/JCR-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3121:
-------------------------------
Fix Version/s: (was: 2.2.10)
> InternalVersionManagerBase.getVersionHistoryOfNode should throw InconsistentVersioningState when it encounters a runtime exception
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-3121
> URL: https://issues.apache.org/jira/browse/JCR-3121
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, versioning
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Attachments: JCR-3121.patch
>
>
> When the versioning persistence is inconsistent (such as broken hierarchy in intermediary nodes), various calls in getVersionHistoryOfNode might fail with runtime exceptions.
> Catch those and report InconsistentVersioningState instead, supplying the node id of the version history; this will enable the versioning fixup to move away the version history (see JCR-3115).
--
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