jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-315) Separate built-in node types from ReadWriteNodeTypeManager
Date Wed, 19 Sep 2012 15:00:07 GMT

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

Marcel Reutegger commented on OAK-315:

So far my attempt to move the built-in node types to oak-jcr was rather unsuccessful. The
basic problem is how to acquire something like a system session that allows me to perform
the initialization. This is not only a challenge for built-in node types, but also for other
modules as described in OAK-41. I think for now I'll just separate the registration and propose
a generic way to perform initialization in OAK-41.
> Separate built-in node types from ReadWriteNodeTypeManager
> ----------------------------------------------------------
>                 Key: OAK-315
>                 URL: https://issues.apache.org/jira/browse/OAK-315
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, jcr
>            Reporter: Marcel Reutegger
>            Priority: Minor
> Registration code for built-in node types are currently in ReadWriteNodeTypeManager.
I think this should be separate from the more generic node type management. Triggering the
registration in ContentSession also looks strange to me.
> I suggest we move the built-in node type registration to oak-jcr for now. I think oak-core
or more specifically ContentSession shouldn't have to know about built-in node types or plugins
in general.

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

View raw message