[
https://issues.apache.org/jira/browse/OAK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated OAK-1126:
-------------------------------
Attachment: 0001-OAK-1126-Same-node-and-property-name-support.patch
Attached a draft patch that outlines the MicroKernel changes that would be
required.
Basically I'd decouple the tree structure from the "node object" so that we can
keep the simple node-as-a-JSON-object approach, just reinterpreted so that the
node object consists of just the properties of the node. Child nodes (that are
already handled differently with offset/limit, separate filters, etc.) are
included as entries within an extra ":children" object.
AFAICT the only change to the JSOP format would be to adjust the addNode syntax
to use the ":children" mechanism for child nodes. All other JSOP operators
already treat nodes and properties separately (for example there's different
syntax for removing nodes vs. removing properties), so there's no risk of
confusion between node and property paths.
> 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: 0001-OAK-1126-Same-node-and-property-name-support.patch,
> 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)
