jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-414) Importing protected properties
Date Thu, 01 Nov 2012 16:05:12 GMT

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

angela commented on OAK-414:

in revision: 1404623 i added another package to oak-spi containing a slightly modified
version of protected item import facility that we used to have in jackrabbit core. in
particular i completely dropped the distinction between methods used for workspace
vs session import.

in addition i modified the security related configurations that they can expose
their implementation specific importer functionality.

currently this code is not used in the XML-importer which IMO needs some major
refactoring in order to really provide support for the full JCR import functionality.
in a next step, i would verify if the initial draft was suitable to cover
user information.

feel free to adjust or modify it, if there is something missing or not suitable.

> Importing protected properties
> ------------------------------
>                 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

View raw message