[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410110#comment-13410110
]
Thomas Mueller commented on OAK-169:
------------------------------------
Could we discuss this in the next meeting? I think orderable child nodes are
not important if the default order of child nodes is sorted by node name. If
the default order (even if it's a stable order) appears to be random for a
human, then he is very tempted to use orderable child nodes. If the default
order is sorted by name, then Carstens use case probably wouldn't need
orderable child nodes.
A use case similar to what Carsten described is a "log file node". Each child
node is a new entry in the log file, and new entries are appended using a
timestamp, to the end of the log file. The log file could grow very large. To
display a part of the log file, one could use name patterns such as
node.getNodes("2012-01-12 15:*") to get all entries for the given hour.
> 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
