[jira] [Resolved] (SLING-12950) Prevent exposing the sling:resourceType from JCR Resource Resolver if just derived from jcr:primaryType

["Konrad Windszus (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved SLING-12950.
-------------------------------------
    Resolution: Fixed

The feature from SLING-12781 has been reverted with https://github.com/apache/sling-org-apache-sling-jcr-resource/commit/18a2ed791068cff0c5d0d3e36042c771dea30f5f.

> Prevent exposing the sling:resourceType from JCR Resource Resolver if just derived from jcr:primaryType
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-12950
>                 URL: https://issues.apache.org/jira/browse/SLING-12950
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: JCR Resource 3.3.6
>
>
> In the context of SLING-12781 the "sling:resourceType" was exposed as property even if derived from the underlying JCR property "jcr:primaryType". This turned out to cause issues with consumers that rely on the fact that all exposed resource properties from the JCR resource provider are backed by real JCR properties.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)