[ 
https://issues.apache.org/jira/browse/SLING-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649558#comment-13649558
 ] 

Alexander Klimetschek commented on SLING-2853:
----------------------------------------------

Namespacing sling:members sounds good. However, having both jcr:content and 
sling:members intermediary nodes is too much and does not solve anything - you 
still have a potential conflict with either node. But hhe namespaced 
sling:members would be enough to safely protect against that.

Renaming sling:members to jcr:content would be great as well (IMHO a good 
standard JCR name for this), but I understood that such a resource API level 
implementation in Sling should be free of jcr-specifics.
                
> 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
>            Assignee: Felix Meschberger
>            Priority: Minor
>         Attachments: collection_v2.zip, collection_v3.zip, collection_v4.zip, 
> 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

Reply via email to