[
https://issues.apache.org/jira/browse/JCR-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570085#comment-13570085
]
Unico Hommes commented on JCR-3507:
-----------------------------------
Hi [~anchela],
I took looked around for the most logical way to add such a check and I think I
found it in AccessManager#checkRepositoryPermission.
VersionHistoryImpl#removeVersion already checks whether the *session* has
Permission#VERSION_MNGMT with a call to AccessManager#checkPermission.
For those sensitive cases such as removing a version and a version history we
could do an additional check for Permission#VERSION_MNGMT at the *repository*
level using a call to AccessManager#checkRepositoryPermission.
WDYT?
> Make it possible to remove version histories via the internal version
> management API
> ------------------------------------------------------------------------------------
>
> Key: JCR-3507
> URL: https://issues.apache.org/jira/browse/JCR-3507
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, versioning
> Reporter: Unico Hommes
> Assignee: Unico Hommes
> Fix For: 2.7
>
>
> Version histories can become orphaned. This happens when the subject node is
> removed from the repository. In order to deal with the problem of
> indefinitely growing data stores, it should be possible to create
> functionality that removes such orphaned version histories.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
