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

Hardcoded "childOrder" in NodeDelegate

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.4
    • core, jcr
    • None

    Description

      there has been some discussion recently on how to deal with internal (hidden?) content
      such as for example the property reflecting the order of child nodes (see http://markmail.org/message/kzt7csiz2bd5n3ww).

      while working on some initial permission code i found that currently that property name
      is hardcoded in multiple places in NodeDelegate while at the same time the javadoc of
      NodeDelegate#getChildren refers to a different property name.

      until we reach consensus on how to deal with such internal content, if/how to hide it from
      JCR API consumers and whether or not (and to which extend) that should be a implementation
      detail of oak-core, i would suggest to define at least a constant on PropertyState that
      allows to easily identify and adjust all usages.

      Attachments

        Activity

          People

            Unassigned Unassigned
            angela Angela Schreiber
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: