[
https://issues.apache.org/jira/browse/SLING-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951120#comment-17951120
]
Carsten Ziegeler commented on SLING-12781:
------------------------------------------
I would leave AbstractResource untouched rather implement it in every resource
provider in the real resources (which I think we did). Changing
AbstractResource might be too dangerous as the blast radius might be very large
> Expose resource type and resource type always also via getValueMap()
> --------------------------------------------------------------------
>
> Key: SLING-12781
> URL: https://issues.apache.org/jira/browse/SLING-12781
> Project: Sling
> Issue Type: Bug
> Components: API
> Reporter: Konrad Windszus
> Priority: Major
>
> As discussed in
> https://lists.apache.org/thread/qfj6m7tkvkyz1zvx0fc93385yp1ho04j the resource
> type and the optional super type should always be exposed as regular
> properties {{sling:resourceType}} and {{sling:resourceSuperType}} via the
> resource's valuemap.
> Also setting those properties via
> [ModifiableResourceType|https://sling.apache.org/apidocs/sling13/org/apache/sling/api/resource/ModifiableValueMap.html]
> should modify the return value of {{Resource.getResourceType()}} an
> {{Resource.getResourceSuperType()}}.
> This allows to also set the type/super type in the
> {{ResourceResolver.create(...)}} method via the properties arguments (no
> matter which resource provider is serving the new resource)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
