[
https://issues.apache.org/jira/browse/SLING-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434686#comment-17434686
]
Konrad Windszus commented on SLING-7975:
----------------------------------------
I think we can maybe start with just supporting ordering among a single
provider. That should cover 99% of the cases already. Ordering among multiple
providers can be added later if really necessary.
> Add a Java API for ordering resources
> -------------------------------------
>
> Key: SLING-7975
> URL: https://issues.apache.org/jira/browse/SLING-7975
> Project: Sling
> Issue Type: New Feature
> Components: API
> Reporter: Jean-Christophe Kautzmann
> Priority: Major
>
> Sling should provide an API (e.g. in Resource, ResourceResolver or
> ResourceUtil) to order resources, similar to what the JCR API provides:
> [https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/Node.html#orderBefore(java.lang.String,%20java.lang.String])
>
> This would help avoid having to use the JCR API.
>
> The implementation is already available at:
> [https://github.com/apache/sling-old-svn-mirror/blob/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/AbstractPostOperation.java#L411]
>
> It is only a matter of exposing it as part of the Sling API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
