jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1126) Same node and property name support
Date Tue, 05 Nov 2013 09:20:17 GMT

    [ https://issues.apache.org/jira/browse/OAK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813798#comment-13813798
] 

Stefan Guggisberg commented on OAK-1126:
----------------------------------------

bq. This was never a use case. From the beginning on oak-core was deemed to be the only client
to the MicroKernel ever.

i beg to differ. the MicroKernel API was designed to be portable from scratch. therefore it's
obvious that it's possible to implement and use it in different languages/stacks (e.g. c,
nodejs, etc).

> 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, 0002-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)

Mime
View raw message