>Am 22.05.15 um 14:51 schrieb Stefan Seifert: >> this is another idea from Santiago García Pimentel an API extension that >affects both ResourceProvider SPI and the Resource/ResourceResolver API. >> >> Provide a mechanism to order resources >> https://issues.apache.org/jira/browse/SLING-4741 >> >> some resource provider like JCR/oak can support this, others may not (e.g. >the nosql resource provider currently always returns the resources sorted >alphabetically to avoid storage of complex ordering info). >> >Right, good idea - I would leave it out for the moment. But for the next >API we should definitely consider this.
Sling API v4...? at least when working with JCR this is not an uncommon usecase. this would affect several methods - create, copy, move etc. stefan
