[
https://issues.apache.org/jira/browse/SLING-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16536796#comment-16536796
]
Konrad Windszus commented on SLING-7377:
----------------------------------------
The query would then need to be composed of all derived resource types as well,
i.e. the search query would be concatenated out of multiple resource type
conditions.
> Expose derived resource types for a given resource type
> -------------------------------------------------------
>
> Key: SLING-7377
> URL: https://issues.apache.org/jira/browse/SLING-7377
> Project: Sling
> Issue Type: Improvement
> Components: API, ResourceResolver
> Affects Versions: API 2.16.4
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently {{sling::resourceSuperType}} properties are only evaluated in the
> Sling Servlet Resolver and it is only possible to retrieve the super type of
> a given type (via {{Resource.getResourceSuperType()}}
> (https://issues.apache.org/jira/browse/SLING-278) but not vice versa.
> For the use case of e.g. searching for content of resource type {{a}} or any
> type derived from {{a}} it is necessary to know all resource types derived
> from {{a}} (direct or transitive) up front.
> For that I propose to extend the {{ResourceResolver}} interface with an
> additional method which retrieves all derived resource types for a given type.
> There was an initial discussion about this in
> https://www.mail-archive.com/[email protected]/msg73080.html.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
