[jira] [Commented] (SLING-4340) SLING-4247 created odd side-effects

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286286#comment-14286286 ] 

Carsten Ziegeler commented on SLING-4340:
-----------------------------------------

[~justinedelson] I think that change is wrong, it assumes that resources use the sling:resourceType property which is not required, and your /apps/a/1/a resource shows that it's not the case. What if that resource had "sling:resourceType" set to "nt:unstructured" ? Then you would end up with the same problem

> 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)