[SLING-11506] Streamline and document resource (super) type merging

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Merger 1.4.0
• Fix Version/s: Resource Merger 1.4.2
• Component/s: Extensions
• Assignee: Carsten Ziegeler
• Reporter: Konrad Windszus
• Created: 02/Aug/22 08:50
• Updated: 17/Mar/23 15:02
• Resolved: 15/Feb/23 13:06

Description

In SLING-4340 the merging of resource types has been changed so that it gives the resourceType property precedence over Resource.getResourceType() (https://github.com/apache/sling-org-apache-sling-resourcemerger/blob/f821f844ba675e3850189debf8e45239026c5709/src/main/java/org/apache/sling/resourcemerger/impl/MergedResource.java#L74-L92).

This change is questionable and kind of unexpected from the user's side and also leads to undesired side effects like outlined in SLING-11504.

So in the best case the merging of resource types doesn't rely on properties (which are implementation details of the underlying resolvers) but clearly derives from either the lowest or highest resource without breaking the use cases outlined in SLING-4340.

Issue Links

• relates to: SLING-4340 Improve resource type handling
• relates to: SLING-11504 BundleResource fallback sling:resourceType should be consistent with JcrNodeResource