[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408011#comment-13408011
]
Jukka Zitting commented on OAK-169:
-----------------------------------
bq. just record the differences
Unfortunately this doesn't work. The outcome of the referenced thread was the
following definition for the stability of child node ordering:
{code:none}
Multiple iterations are guaranteed to return the child nodes in the same order,
but the specific order used is implementation-dependent and may change across
different states of the same node.
{code}
We of course change that if we really need to, but doing so requires modifying
the MicroKernel contract. I'm not convinced that this use case is strong enough
for that.
bq. The parent would point to the first child node, the first child node point
to the second child node, and so on.
That would only work if we adjust the MicroKernel contract and require the MK
implementation to do that. As mentioned, I don't see a strong enough use case
for that.
> 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
