[
https://issues.apache.org/jira/browse/JCR-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131500#comment-13131500
]
Julian Reschke commented on JCR-3121:
-------------------------------------
Revised plan: modify VersionManager so that we can get the history node id
upfront; this will enable the versioning fixup to do the "right" thing without
having too touch even more pieces of code.
> 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
> Fix For: 2.2.10, 2.3.2
>
> 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
