[ https://issues.apache.org/jira/browse/OAK-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Marth updated OAK-41: ----------------------------- Fix Version/s: (was: 0.12) 0.14 > Initial repository setup > ------------------------ > > Key: OAK-41 > URL: https://issues.apache.org/jira/browse/OAK-41 > Project: Jackrabbit Oak > Issue Type: Task > Components: core > Reporter: angela > Fix For: 0.14 > > Attachments: OAK-41-initial-proposal.patch, > OAK-41-register-namespaces.patch > > > upon the initial creation of a JCR repository the associated SPI layer > (oak-core) should > take care of setting up the corresponding MK-instance. this includes > (incomplete list): > - create the jcr repo (not sure what that means in terms of mk-implementation) > - create the jcr:system node (unique for the repository, across workspaces) > - create the default workspace (-> name from config) > - create the root node of the default workspace > in addition the repository would need to have access to the following > information (maybe also mk-nodes underneath jcr:system ??) > - built-in node types > - built-in namespace > - built-in privileges > - built-in permissions > - repository configuration (can that be stored in the mk?) > as far as the workspace is concerned a functional repository would in > addition need to have: > - build-in users (based on some sort of configuration) > - workspace configuration -- This message was sent by Atlassian JIRA (v6.1#6144)