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 2012/12/14 15:34:12 UTC
[jira] [Resolved] (OAK-494) Cleanup ReadOnlyNodeTypeManager
[ https://issues.apache.org/jira/browse/OAK-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved OAK-494.
------------------------
Resolution: Fixed
hopefully found and fixed all bogus name comparison (jcr-jcr, jcr-oak,
oak-jcr)... the additional interfaces implemented by ReadOnlyNodeTypeManager
has been adjusted to explicitly state if oak or jcr name is expected.
there one minor oddity left in ReadWriteNodeTypeManager#registerNodeTypes(Reader cnd) where the template name is compared against NT_BASE and - in case of
empty super types - NT_BASE is added as declared super type... i wasn't totally
sure if that one really needs a fix.
> Cleanup ReadOnlyNodeTypeManager
> -------------------------------
>
> Key: OAK-494
> URL: https://issues.apache.org/jira/browse/OAK-494
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: angela
> Assignee: angela
>
> while looking at different issues i found that we have some inconsistencies
> and issues with the usage of jcr vs oak name in the node type plugin.
--
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