[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410332#comment-13410332
]
Michael Dürig commented on OAK-169:
-----------------------------------
Thanks for digging this up. Citing from that message:
bq. for getChildNodeEntries() we can therefore drop the distinction between
user-defined and native order and just state that the iteration order is stable.
There is currently no statement about iteration order stability in the
Microkernel API contract. But the stability which the underlying implementation
provides (AFICS) is too weak for implementing efficient support for ordering on
top of it. As I [said
earlier|https://issues.apache.org/jira/browse/OAK-169?focusedCommentId=13410174&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13410174]
I'm fine with that and we should use the multi valued property if we need a
stable order and/or orderability.
> 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
