[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407045#comment-13407045
]
Jukka Zitting commented on OAK-168:
-----------------------------------
Note that a versioning implementation should also take the somewhat unique
access control implications of versioning into account. For example, is access
to a version history controlled separately, or does it follow the access
controls of the latest checked out version? What about a version history with
no checked out version?
> Basic JCR VersionManager support
> --------------------------------
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Jukka Zitting
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
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
