jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-168) Basic JCR VersionManager support
Date Wed, 08 May 2013 14:07:18 GMT

    [ https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651910#comment-13651910
] 

Marcel Reutegger commented on OAK-168:
--------------------------------------

Note on compatibility and spec compliance:

The current Jackrabbit implementation shows a strange behaviour for the versionable state
on checkin of a versionable node. Even for OPV copy, the child nodes under the jcr:frozenNode
are of type nt:frozenNode. This leads to some strange state of the child node, because it
always has a jcr:frozenUuuid property even if the source node is not mix:referenceable. For
Oak I'd like to implement it spec compliant and use the node type of the child node as is.

This will have some impact on existing applications migrating to Oak. E.g. the result of a
query may be different because nodes from the version storage now match the primary type from
the nodes in the workspace.
                
> Basic JCR VersionManager support
> --------------------------------
>
>                 Key: OAK-168
>                 URL: https://issues.apache.org/jira/browse/OAK-168
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: jcr
>            Reporter: Jukka Zitting
>            Assignee: Marcel Reutegger
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message