[
https://issues.apache.org/jira/browse/OAK-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-414:
-----------------------
Summary: Importing protected properties and nodes (was: Importing
protected properties)
> 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
>
> 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
