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

Tobias Bocanegra commented on OAK-1126:
---------------------------------------

I suggest to go with a compromise:
# let the persistence layer determine if SNNP is supported or not
# don't add any SNNP related checks in the Oak layer and assume it's supported.

advantages:
* the MK API can stay the same
* no unnecessary checks in the Oak layer to check for colliding SNNP
* Oak is backward compatible to JR2.x with persistence implementations that 
support SNNP

disadvantages:
* we need to introduce a capabilities interface to the persistence layer
* Oak clients need to be aware that depending on the persistence used, the 
repository could behave differently, and need to check the respective 
repository descriptor (which they should anyways :-)

changes:
* the value of the {{option.node.and.property.with.same.name.supported}} 
descriptor needs to be provided by the persistence layer
* disable SNNP support in the MKs
* enable SNNP support in the NodeStores

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

Reply via email to