You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2012/07/23 18:05:34 UTC

[jira] [Created] (OAK-203) Basic same name sibling support

Jukka Zitting created OAK-203:
---------------------------------

             Summary: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira