You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2025/09/24 13:51:00 UTC
[jira] [Commented] (SLING-12781) Expose resource type and resource super type always also via getValueMap()
[ https://issues.apache.org/jira/browse/SLING-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18022432#comment-18022432 ]
Konrad Windszus commented on SLING-12781:
-----------------------------------------
Partially reverted (for JCR Resource) in SLING-12950.
> Expose resource type and resource super 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
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: JCR Resource 3.3.4, API 3.0.0
>
>
> 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)