You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Amit Gupta (JIRA)" <ji...@apache.org> on 2013/07/29 07:21:47 UTC

[jira] [Commented] (SLING-2982) add getMembers() api to ResourceCollection

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

Amit Gupta commented on SLING-2982:
-----------------------------------

> There is a public static ResourceCollectionConstants.MEMBERS_NODE_NAME which gave me the feeling that there should be an API that would return these values.  If this is not the case then I thought it would have been protected or private.
This is in impl package, and not exported.

                
> add getMembers() api to ResourceCollection
> ------------------------------------------
>
>                 Key: SLING-2982
>                 URL: https://issues.apache.org/jira/browse/SLING-2982
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Resource Collections 1.0.0
>            Reporter: Amit Gupta
>            Priority: Minor
>             Fix For: Resource Collections 1.0.0
>
>
> Feedback on mailing list from bhellema@adobe.com
> I also have a requirement to iterate through the sling:members in the collection and pull the properties off the nodes to render UI, however this isn't simple enough to do with the current API.  The two apis we have to use are getResources(), and getProperties() are do not reference the same resources which muddies the water.  It would be nice to have a getMembers() API that would return you the sling:members which then you could iterate over.  
> There is a public static ResourceCollectionConstants.MEMBERS_NODE_NAME which gave me the feeling that there should be an API that would return these values.  If this is not the case then I thought it would have been protected or private.

--
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