You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2013/02/19 12:49:12 UTC

[jira] [Created] (OAK-640) Add WorkspaceInitializer

angela created OAK-640:
--------------------------

             Summary: Add WorkspaceInitializer
                 Key: OAK-640
                 URL: https://issues.apache.org/jira/browse/OAK-640
             Project: Jackrabbit Oak
          Issue Type: New Feature
            Reporter: angela


i had another look at various RepositoryInializer and in particular at
the way the UserInitializer is created to ensure proper indexing coming
to the conclusion that the latter isn't an actual RepositoryInitializer
as it will only work properly in a context where the basic repository
setup is already available (commit hooks, index configuration, node types,
security configuration etc). furthermore the current default implementation is intended to keep user information on a workspace level.

so, what while we try to do everything with the RepositoryInitializer
we are actually missing another level of init and i'd suggest to add 
another interface to the spi.lifecycle package that covers initialization 
of what can be considered "workspace" information. that separate initializers would only be called after the global repo setup is being completed and
would already be aware of the individual configuration settings like
indexes, commit hooks and so forth.

since we don't have support for multiple workspaces right now we can 
keep our single workspace setup along with the OAK#createContentRepository
call such that we can still move it to the proper location that was responsible of initializing a new workspace upon creation.

i will take another look and provide an initial draft for further 
discussions. the overall goal was to ensure proper "workspace" setup
without hardcoding the indexprovider, security setup and the commit hooks 
in the userinitializer.

--
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