[SLING-1024] Correct resource super type handling

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Servlets Resolver 2.0.6, JCR Resource 2.0.4, Engine 2.0.4, API 2.0.4
• Fix Version/s: Servlets Resolver 2.0.8, JCR Resource 2.0.6, Engine 2.0.6, API 2.0.6
• Component/s: API, Engine, JCR, Servlets
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 26/Jun/09 14:04
• Updated: 13/Sep/09 13:23
• Resolved: 26/Jun/09 14:48

Description

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