[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469262#comment-13469262
]
angela commented on OAK-169:
----------------------------
that's a perfect move. i definitely prefer that over the previous approach that
delegated
the complete reordering to the implementation on top of oak. similarly i think
having
an extra api method to cover reordering of nodes makes sense... for the save of
flexibility
i would however prefer a more general method (reorder() or similar)... while
'orderBefore'
has a 1:1 match with the jcr api, i don't particularly like it as it feels a bit
awkward to use, when you want to move something to the start or to the end.
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
