[
https://issues.apache.org/jira/browse/SLING-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-1024:
-------------------------------------
Component/s: (was: Servlets Resolver)
(was: JCR Resource)
Servlets
JCR
> Correct resource super type handling
> ------------------------------------
>
> Key: SLING-1024
> URL: https://issues.apache.org/jira/browse/SLING-1024
> Project: Sling
> Issue Type: Improvement
> Components: API, Engine, JCR, Servlets
> Affects Versions: Servlets Resolver 2.0.6, JCR Resource 2.0.4, Engine
> 2.0.4, API 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Servlets Resolver 2.0.8, Engine 2.0.6, API 2.0.6, JCR
> Resource 2.0.6
>
>
> A resource should only return a super resource type if it has configured one.
> Currenty the jcr resource node implementation does a lookup of the resource
> representing its resource type to get the resource super type from there if
> it doesn't have a super type set.
> This logic should solely be called from the script resolver (and not be tied
> to a resource implementation).
> In this respect, the bundle resource should return "sling/bundle/resource" as
> it's super type and not null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
