You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2011/07/26 22:36:10 UTC

[jira] [Updated] (SLING-2158) JsonSerialization: Add new ":order" JSON array to transport child node ordering when needed

     [ https://issues.apache.org/jira/browse/SLING-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Bocanegra updated SLING-2158:
------------------------------------

    Summary: JsonSerialization: Add new ":order" JSON array to transport child node ordering when needed  (was: JsonSerialization: Add new ":oder" JSON array to transport child node ordering when needed)

> JsonSerialization: Add new ":order" JSON array to transport child node ordering when needed
> -------------------------------------------------------------------------------------------
>
>                 Key: SLING-2158
>                 URL: https://issues.apache.org/jira/browse/SLING-2158
>             Project: Sling
>          Issue Type: New Feature
>          Components: Servlets
>            Reporter: Tobias Bocanegra
>            Priority: Minor
>
> as discussed in:
> http://mail-archives.apache.org/mod_mbox/sling-dev/201104.mbox/%3CBANLkTimaU-CV5fHYYrX-z5Ktn4afMFqw9A@mail.gmail.com%3E
> i suggest to add a new array property containing the child node names to the default JSON renderer if 'requested' with an 'order' selector.
> i would include the child node names also on the end of the depth limit. this allows to get the child node names without the need to load them with a deeper request:
> eg:
> GET /content/en.0.order.json would return:
> {
> "title": "Hello, world",
> ":oder": ["sub1", "sub2"]
> }

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira