[SLING-4340] Improve resource type handling

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Resource Merger 1.2.4
• Assignee: Carsten Ziegeler
• Reporter: Justin Edelson
• Created: 21/Jan/15 17:03
• Updated: 02/Aug/22 08:53
• Resolved: 03/Feb/15 12:04

Description

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/a").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.

Issue Links

• is related to: SLING-11506 Streamline and document resource (super) type merging
• relates to: SLING-4247 Reconsider resource type handling