[
https://issues.apache.org/jira/browse/SLING-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572089#comment-13572089
]
Justin Edelson commented on SLING-2723:
---------------------------------------
I'd suggest adding it to ResourceUtil first and then to
Resource/ResourceResolver if it is necessary. Presumably, the latter methods
would end up just referencing the former (i.e. in the case of AbstractResource).
One request - could we call the interface ResourceFilter, not just Filter?
Regarding the specification pattern, I would assume that this could be used
(possibly along with a Builder) to implement the ResourceFilter interface.
> Add listChildren(Filter<Resource> filter) to Resource
> -----------------------------------------------------
>
> Key: SLING-2723
> URL: https://issues.apache.org/jira/browse/SLING-2723
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: API 2.3.0
> Reporter: Feike Visser
> Priority: Minor
>
> Currently there is Resource.listChildren(), this will return all the children
> of this resource.
> This improvement is to add a listChildren(Filter<Resource> filter) method
> where you can specify a specific filter to limit the result, so you don't
> have to code a loop yourself.
> An example can found in the Page-interface.
--
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
