You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2015/01/21 18:06:34 UTC
[jira] [Resolved] (SLING-4340) SLING-4247 created odd side-effects
[ https://issues.apache.org/jira/browse/SLING-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson resolved SLING-4340.
-----------------------------------
Resolution: Fixed
Assignee: Justin Edelson
In r1653604, I changed the logic so that it first tries to use the sling:resourceType property and then falls back to the first non-null getResourceType() return value.
[~cziegeler] can you take a look?
> SLING-4247 created odd side-effects
> -----------------------------------
>
> Key: SLING-4340
> URL: https://issues.apache.org/jira/browse/SLING-4340
> Project: Sling
> Issue Type: Bug
> Reporter: Justin Edelson
> Assignee: Justin Edelson
> 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").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)