jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manfred Baedke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-414) Importing protected properties and nodes
Date Tue, 07 May 2013 12:01:19 GMT

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

Manfred Baedke commented on OAK-414:

Current status: The session import is functional. Essentially it has been ported from Jackrabbit,
along with all test cases that do not use workspace import or use config options of the user/ACL
import that are not (yet) available in Oak (details will follow). The current implementation
uses the JCR API. The next step will be to implement the workspace import based on the Oak
API, ideally in a way that allows to use it for a session import, too.
> Importing protected properties and nodes
> ----------------------------------------
>                 Key: OAK-414
>                 URL: https://issues.apache.org/jira/browse/OAK-414
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: jcr
>            Reporter: angela
>            Assignee: Manfred Baedke
> for backwards compatibility with jackrabbit we should also implement
> the ability to import protected items.
> while import version content is most probably unique and system defined,
> there are quite some areas like user management and access control that
> need to be pluggable and thus the particular import behavior should be
> defined by the corresponding implementation.
> i envision this to work in a similar way than the implementation
> specific validators.
> steps to get there include:
> - properly setup the xml-import such that it recognizes protected items
>   and calls the configured protected-item-importers.
> - allow to plugin implementation specific extensions
> - define an interface for that protected item import.
> regarding the latest part: in contrast to jackrabbit core, where we had
> just the JCR API at hand i would suggest to setup those special importers
> such that they can operate both on the JCR API (session and extensions)
> and on the OAK API giving the implementation more flexibility on how
> to actually treat the import.

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

View raw message