[
https://issues.apache.org/jira/browse/SLING-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649385#comment-13649385
]
Amit Gupta edited comment on SLING-2853 at 5/5/13 6:10 PM:
-----------------------------------------------------------
> If you look at the code, it's actually simpler. The current code already
> relies on the "pathorder" property for the order, which needs to keep all
> references anyway for it to work.
code is simpler, but if you look at it will eventually add inconsistencies.
such that getEntries returns a iterator over resources which represent entries
in collection. So, for simple entries, I actually can not return the entries.
That is the reason why I didn't try to do that optimization.
GetEntries is needed otherwise, there is no way to return the additional
properties stored with an entry in collection.
was (Author: amitxlnc):
> If you look at the code, it's actually simpler. The current code already
relies on the "pathorder" property for the order, which needs to keep all
references anyway for it to work.
code is simpler, but if you look at it will eventually add inconsistencies.
such that getEntries returns a iterator over resources which represent entries
in collection. So, for simple entries, I actually can not return the entries.
That is the reason why I didn't try to do that optimization.
> Add ResourceCollection to Sling
> -------------------------------
>
> Key: SLING-2853
> URL: https://issues.apache.org/jira/browse/SLING-2853
> Project: Sling
> Issue Type: New Feature
> Components: API
> Affects Versions: API 2.0.2
> Reporter: Amit Gupta
> Priority: Minor
> Attachments: collection.zip, resourcecollection.zip
>
>
> Creating a collection of resources has been a use case for a while and there
> has been no inherent support in SLING for the same.
> This proposal is to add a ResourceCollection interface and implementation
> that allows creation of collection of resources.
> Collection is a simple list of members, where each member contains path of
> resource it refers to. In future, we might need to store additional
> information with the member, hence following structure is proposed
> N: resourceCollection (nt:unstructured)
> + P: sling:resourceType
> + N : members (nt:unstructured)
> + N: member_res1 > nt:unstructured
> + P: path > string, reference to actual resource
> + N: member_res2 > nt:unstructured
> + P: path > string, reference to actual resource
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
