[
https://issues.apache.org/jira/browse/OAK-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-41:
-------------------------------
Attachment: OAK-41-register-namespaces.patch
Patch to add support for registering default Namespaces in addition to the node
types. Without this change was getting following exception while importing
packages
{noformat}
Caused by: javax.jcr.NamespaceException: No namespace registered for prefix oak
at
org.apache.jackrabbit.oak.plugins.name.ReadOnlyNamespaceRegistry.getURI(ReadOnlyNamespaceRegistry.java:100)
at
org.apache.jackrabbit.oak.jcr.SessionImpl.getNamespaceURI(SessionImpl.java:505)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.sling.jcr.base.SessionProxyHandler$SessionProxyInvocationHandler.invoke(SessionProxyHandler.java:109)
at $Proxy9.getNamespaceURI(Unknown Source)
at
org.apache.jackrabbit.spi.commons.namespace.SessionNamespaceResolver.getURI(SessionNamespaceResolver.java:59)
{noformat}
> 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,
> 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 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
