[
https://issues.apache.org/jira/browse/SLING-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-12781.
-------------------------------------
Fix Version/s: JCR Resource 3.3.4
API 3.0.0
Resolution: Fixed
Fixed in
https://github.com/apache/sling-org-apache-sling-api/commit/0fc8622cf1fdb0236039586e11da5fc6a044563b
(Sling API) and
https://github.com/apache/sling-org-apache-sling-jcr-resource/commit/fe35d53a1b0f8ff1a7616909f16539b759bd0bdd
(JCR Resource)
> 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)
