[
https://issues.apache.org/jira/browse/SLING-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254007#comment-13254007
]
Tobias Bocanegra commented on SLING-2457:
-----------------------------------------
Resource type resolution should work independent of the access permissions. The
same is already true for script resolution. i.e. the request to
/content/component/foo would already resolve to a script in components/bar2 (if
not present in components/bar).
> ResourceUtil.isA() fails if resource has a type, whose super type is not
> readable
> ---------------------------------------------------------------------------------
>
> Key: SLING-2457
> URL: https://issues.apache.org/jira/browse/SLING-2457
> Project: Sling
> Issue Type: Bug
> Components: API
> Affects Versions: API 2.2.0
> Reporter: Tyson Norris
>
> * define a resource at /content/component/foo whose type is
> myapp/components/bar
> * define bar at /apps/myapp/components/bar
> * on /apps/myapp/components/bar, set sling:resourceSuperType as
> /libs/components/bar2
> If resolver from resource.getResourceResolver() cannot access
> /libs/components/bar2, then ResouceUtil.isA(resource, "components/bar2")
> returns false, otherwise it returns true.
> There could be an argument that it should not return true in any case,
> however, if you set resourceSuperType on resource as "components/bar2", then
> it returns true with current implementation.
> At least one of these is wrong, I think.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
