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 "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2013/11/14 03:05:20 UTC

[jira] [Reopened] (OAK-1126) Same node and property name support

     [ https://issues.apache.org/jira/browse/OAK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Bocanegra reopened OAK-1126:
-----------------------------------


> 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
>            Assignee: Tobias Bocanegra
>             Fix For: 0.11
>
>         Attachments: 0001-OAK-1126-Same-node-and-property-name-support.patch, 0002-OAK-1126-Same-node-and-property-name-support.patch, OAK-1126.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> 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)