[
https://issues.apache.org/jira/browse/OAK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809367#comment-13809367
]
angela edited comment on OAK-1126 at 10/30/13 5:30 PM:
-------------------------------------------------------
as discussed today in the oak-meeting: i tried it out to see if OAK would
really work with the corresponding descriptor enabled. attached a patch that
shows the effect and includes some extra tests (could not find the tests in the
TCK).
was (Author: anchela):
as discussed today in the oak-meeting: i tried it out to see if OAK would
really work with the corresponding descriptor enabled. the attached a patch
that shows the effect and includes some extra tests (could not find the tests
in the TCK).
> Same node and property name support
> -----------------------------------
>
> Key: OAK-1126
> URL: https://issues.apache.org/jira/browse/OAK-1126
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, doc, jcr
> Reporter: Tobias Bocanegra
> Attachments: OAK-1126.patch
>
>
> The initial MK abstraction mandated that the nodes and properties share the
> same namespace
> (http://wiki.apache.org/jackrabbit/RepositoryMicroKernel#Data%20Model). This
> is a regression from Jackrabbit 2.x, which supports same name nodes and
> properties (SNNP).
> OTOH, the NodeStores can easily support SNNP and with proper escaping, the
> MKs can also support it.
> We should try to keep the support for SNNP in order to keep backward
> compatibility for existing content, and also keep the support for importing
> XML documents with same attribute and element names.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
