On Wed, Apr 20, 2016 at 2:17 PM, Nicolas Peltier <[email protected]> wrote:
>>...the alternative being to extend the POST servlet to do what
>> you need, as it's generally useful.
> right, how would you see it? custom key value like
> “slingpost_order”:[“child1”,”child2”,”child3”] ? ...
That won't scale if you have many objects, how about submitting
content as a json array, maybe something like this:
{
"title": "The parent node",
"SLING:ordered": [{
"SLING:name": "first",
"title": "This comes first"
}, {
"SLING:name": "second",
"title": "This comes second"
}]
}
This needs to be triggered by selector or content-type switch so that
the existing POST behavior is unchanged.
I suppose having SLING:ordered should then also set the appropriate
mixin on the parent node.
-Bertrand
