[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407913#comment-13407913
]
Julian Reschke edited comment on OAK-169 at 7/6/12 11:52 AM:
-------------------------------------------------------------
I believe the idea is to have only a partial ordering (you can rely on the
order of only those entries that have been re-ordered).
Not sure how well this is going to work in practice, because that wouldn't
satisfy the requirements in
http://www.day.com/specs/jcr/2.0/23_Orderable_Child_Nodes.html (namely that the
ordering is consistent for *all* child nodes, and that new nodes are added to
the end).
was (Author: reschke):
I believe the idea is to have only a partial ordering (you can rely on the
order of only those entries that have been re-ordered).
Not sure how well this is going to work in practice...
> 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
