[SLING-10844] ResourceMapper.getMapping() returns null for empty path and unreadable root

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Resolver 1.7.0
• Fix Version/s: Resource Resolver 1.10.0
• Component/s: ResourceResolver
• Assignee: Carsten Ziegeler
• Reporter: Mohit Arora
• Created: 28/Sep/21 19:52
• Updated: 16/Mar/23 10:24
• Resolved: 08/Aug/22 13:11

Description

After the bug fix for SLING-9620, the behavior for ResourceMapper.getAllMappings() was changed such that the mappings list remains empty if the resourcePath provided is an empty string. Prior to this bug fix, the mappings list contained a single entry for empty path.

Since mappings list is empty, ResourceMapper.getMapping() returns null. The javadoc of ResourceMapper.getMapping() API mentions that it will return a non null value if the resourcepath is not null.

We need to decide on the expected behavior here. If mappings list should not be updated in case of empty resourcePath then the API annotation will have to be changed and it can potentially be a backwards incompatible issue in theory as the consumers of the API may not have added a null check to the return value.

Issue Links

• is related to: SLING-9620 ResourceMapperImpl.getAllMappings does not respect multi-valued sling:alias
• is related to: SLING-11511 Allow checking the map/resolve result for an empty path
• is related to: SLING-11513 Allow impersonating an user when checking the result of a map/resolve call