[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412982#comment-13412982
]
Jukka Zitting commented on OAK-169:
-----------------------------------
To push the discussion to a bit more concrete level, I added basic (and still
quite incomplete) support for ordering child nodes using a multi-valued
"childOrder" property (to be renamed once OAK-182 is done). See revisions
1360617 and 1360824.
What's still missing is related node type support (OAK-66), a {{CommitEditor}}
plugin that automatically maintains insertion order when no explicit order is
specified for an orderable node, and figuring out how access control will
interact with this feature.
> 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
