[
https://issues.apache.org/jira/browse/OAK-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866706#comment-13866706
]
Jukka Zitting commented on OAK-1206:
------------------------------------
The reason why I used the Oak namespace for these types was to avoid having to
use the troublesome {{internal}} namespace. But given that for backwards
compatibility we probably can't drop the {{internal}} namespace and that there
should be no need for client code to use these node types, I don't have any
objections to the change.
> Consider renaming internal nodetypes and item names
> ---------------------------------------------------
>
> Key: OAK-1206
> URL: https://issues.apache.org/jira/browse/OAK-1206
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Tobias Bocanegra
> Fix For: 0.15
>
>
> some new nodetypes have the oak namespace but are used only internally. in
> jackrabbit 2.x we used the 'internal' namespace for those.
> I suggest to use the internal namespace for nodes that are not (or should
> not) be created via JCR, namely:
> * rep:NodeType
> * rep:NamedPropertyDefinitions
> * rep:PropertyDefinitions
> * rep:PropertyDefinition
> * rep:NamedChildNodeDefinitions
> * rep:ChildNodeDefinitions
> * rep:ChildNodeDefinition
> see also OAK-1180
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
