jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-203) Basic same name sibling support
Date Thu, 13 Sep 2012 12:31:07 GMT

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

Michael Dürig commented on OAK-203:
-----------------------------------

This approach somewhat interferes with validation of jcr constraints (OAK-66): how should
a child node definition be matched against a same name sibling with an index on it? Currently
it does {{childNodeName.startsWith(nodeDefinition.getName())}} which however can result in
bogus matches.
                
> Basic same name sibling support
> -------------------------------
>
>                 Key: OAK-203
>                 URL: https://issues.apache.org/jira/browse/OAK-203
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>            Reporter: Jukka Zitting
>            Priority: Minor
>
> There are some cases where clients or even the JCR spec expect same name siblings to
be supported. We should have some mechanism to allow such cases to work with no or minimal
required changes. Such a mechanism doesn't need be fully compliant with the SNS feature as
specified by JCR, just good enough to to cover the most common use cases.
> My initial thinking on this is that, whichever way we end up implementing this, it would
be nice if the underlying oak-core and microkernel -level SNS nodes simply used the "name[index]"
naming pattern with no extra semantics associated with it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message