Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-203

Basic same name sibling support

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0
    • Component/s: jcr
    • Labels:
      None

      Description

      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.

        Attachments

        1. OAK-203.patch
          38 kB
          Michael Dürig

          Issue Links

            Activity

              People

              • Assignee:
                mduerig Michael Dürig
                Reporter:
                jukkaz Jukka Zitting
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: