[ https://issues.apache.org/jira/browse/OAK-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810485#comment-13810485 ]
angela commented on OAK-414: ---------------------------- i think we can resolve that fixed. workspace import works in the mean time and the import now uses OAK API instead of JCR API. > 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 was sent by Atlassian JIRA (v6.1#6144)