You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2008/01/16 11:58:37 UTC
[jira] Created: (SLING-167) Default JSON rendering with selectable
depth
Default JSON rendering with selectable depth
--------------------------------------------
Key: SLING-167
URL: https://issues.apache.org/jira/browse/SLING-167
Project: Sling
Issue Type: Improvement
Components: JSON
Reporter: Bertrand Delacretaz
As discussed on list [1], the default JSON rendering should work as follows:
.../mynode.0.json -> returns the node and its properties
.../mynode.1.json -> returns the node, it properties and the direct child nodes and their properties
.../mynode.2.json -> same, but two levels deep in the child nodes hierarchy
...
.../mynode.infinity.json -> returns the entire subtree.
and .../mynode.json behaves like .../mynode.0.json
[1] http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200801.mbox/%3c227048280801090142x32b75287ifc06ca901b329ed0@mail.gmail.com%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-167) Default JSON rendering with selectable
depth
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-167:
------------------------------------
Fix Version/s: 2.0.0
> Default JSON rendering with selectable depth
> --------------------------------------------
>
> Key: SLING-167
> URL: https://issues.apache.org/jira/browse/SLING-167
> Project: Sling
> Issue Type: Improvement
> Components: Commons JSON
> Reporter: Bertrand Delacretaz
> Fix For: 2.0.0
>
>
> As discussed on list [1], the default JSON rendering should work as follows:
> .../mynode.0.json -> returns the node and its properties
> .../mynode.1.json -> returns the node, it properties and the direct child nodes and their properties
> .../mynode.2.json -> same, but two levels deep in the child nodes hierarchy
> ...
> .../mynode.infinity.json -> returns the entire subtree.
> and .../mynode.json behaves like .../mynode.0.json
> [1] http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200801.mbox/%3c227048280801090142x32b75287ifc06ca901b329ed0@mail.gmail.com%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-167) Default JSON rendering with selectable
depth
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz closed SLING-167.
-------------------------------------
Resolution: Fixed
'infinity' recursion level implemented in revision 618936
Note that the o.a.s.commons.json.io.JSONWriter limits this "infinity", the limit was 20 levels and I have increased it to fifty so that my test with a (silly) property named a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y passes.
Silly Tests Values Are Good ;-)
> Default JSON rendering with selectable depth
> --------------------------------------------
>
> Key: SLING-167
> URL: https://issues.apache.org/jira/browse/SLING-167
> Project: Sling
> Issue Type: Improvement
> Components: JSON
> Reporter: Bertrand Delacretaz
>
> As discussed on list [1], the default JSON rendering should work as follows:
> .../mynode.0.json -> returns the node and its properties
> .../mynode.1.json -> returns the node, it properties and the direct child nodes and their properties
> .../mynode.2.json -> same, but two levels deep in the child nodes hierarchy
> ...
> .../mynode.infinity.json -> returns the entire subtree.
> and .../mynode.json behaves like .../mynode.0.json
> [1] http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200801.mbox/%3c227048280801090142x32b75287ifc06ca901b329ed0@mail.gmail.com%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.