[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408004#comment-13408004
]
Thomas Mueller commented on OAK-169:
------------------------------------
> the guarantee of the repository to return the child nodes in some stable order
I would extend that to "return the child nodes in some stable *and user
friendly* order". In my view, returning the nodes ordered by hash code isn't
user friendly. Same as properties files where the key is sorted by hash code -
information is very hard to find once the properties file get larger. If the
keys are sorted by name then that's a lot more user friendly. In that case,
most applications are probably fine (that's my guess) with the provided stable
order, and don't need to re-order the nodes at all.
> Support orderable nodes
> -----------------------
>
> Key: OAK-169
> URL: https://issues.apache.org/jira/browse/OAK-169
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
> Reporter: Jukka Zitting
>
> There are JCR clients that depend on the ability to explicitly specify the
> order of child nodes. That functionality is not included in the MicroKernel
> tree model, so we need to implement it either in oak-core or oak-jcr using
> something like an extra (hidden) {{oak:childOrder}} property that records the
> specified ordering of child nodes. A multi-valued string property is probably
> good enough for this.
--
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
