[
https://issues.apache.org/jira/browse/OAK-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467572#comment-13467572
]
Marcel Reutegger commented on OAK-41:
-------------------------------------
bq. We should probably find a better name than DUMMY_PRINCIPAL. One that
properly reflects its intent.
Agreed. I'm also not too happy with this currently. See also below on pluggable
authentication.
bq. 2nd FIXME in BuiltInNodeTypes.registerBuiltinNodeTypes can be removed
Done in revision 1392779
bq. initialization should IMHO be complete outside the scope of authorization
I agree, that's why I introduced the createRoot(). But based on your feedback I
think it should be possible to get rid of it again. There's already a TODO in
ContentRepositoryImpl about a configurable LoginContextProvider. I think we
should add that to the Oak builder. Then we can provide an implementation that
allows the {{contentRepository.login(null, null)}} proposed by Jukka.
> 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
