[jira] [Commented] (OAK-41) Initial repository setup

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

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

Marcel Reutegger commented on OAK-41:
-------------------------------------

In revision 1392352 I moved the initialization code from ContentRepositoryImpl and ContentSessionImpl to InitialContent (in type plugin of oak-core). RootImpl now has an alternative constructor without a subject to manipulate content in a micro kernel using Oak API classes/interfaces. To make that work I also added new methods to the Oak builder.

I refactored the OSGi related classes in oak-core a bit to get rid of duplicate code and added support for a MicroKernelTracker that hooks into the life cycle of a MicroKernel in an OSGi container. 
                
> 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
>         Attachments: OAK-41-initial-proposal.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 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