You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/02/03 13:04:35 UTC
[jira] [Updated] (SLING-4340) Improve resource type handling
[ https://issues.apache.org/jira/browse/SLING-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-4340:
------------------------------------
Summary: Improve resource type handling (was: SLING-4247 created odd side-effects)
> Improve resource type handling
> ------------------------------
>
> Key: SLING-4340
> URL: https://issues.apache.org/jira/browse/SLING-4340
> Project: Sling
> Issue Type: Bug
> Reporter: Justin Edelson
> Assignee: Carsten Ziegeler
> Fix For: Resource Merger 1.2.4
>
>
> The change made in SLING-4247 created an unfortunate side effect for this scenario:
> /apps/a/1/a - nt:unstructured node, no sling:resourceType property
> /apps/a/2/a - sling:resourceType set to foo/bar
> /apps/a/1 has sling:resourceSuperType set to /apps/a/2
> Then
> resourceResolver.getResource("/mnt/override/apps/a/1/a").getResourceType() will be nt:unstructured
> This strikes me as wrong. And in fact screws up what is for me the main usage of this feature because it shouldn't be necessary to set the sling:resourceType all the time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)