jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3403) Hardcoded "childOrder" in NodeDelegate
Date Fri, 03 Aug 2012 12:43:02 GMT
angela created JCR-3403:
---------------------------

             Summary: Hardcoded "childOrder" in NodeDelegate
                 Key: JCR-3403
                 URL: https://issues.apache.org/jira/browse/JCR-3403
             Project: Jackrabbit Content Repository
          Issue Type: Improvement
            Reporter: angela


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.


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

        

Mime
View raw message