[
https://issues.apache.org/jira/browse/JCR-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140253#comment-13140253
]
Julian Reschke commented on JCR-3121:
-------------------------------------
Rather than doing this we have instead changed the checker code to obtain the
version history node ID as early as possible, which means that there are less
cases we need to piggy-back the node ID to the exception (see JCR-3115).
> 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
>
> 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
