[SLING-12054] WARN of the non-use of optimizedAliasResolution

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Resolver 1.11.0
• Fix Version/s: Resource Resolver 1.11.2
• Component/s: ResourceResolver
• Assignee: Joerg Hoh
• Reporter: Joerg Hoh
• Created: 29/Sep/23 08:57
• Updated: 12/Nov/23 17:31
• Resolved: 05/Oct/23 15:41

Description

As we found in SLING-12025, disabling the optimizedAliasResolution changes the behavior of the mapping result. This can be clearly considered a bug, but as it is part of the ResourceResolver for quite some time (although not default), we cannot fix or remove it that easily.

We should write a WARN message into the log, when the optimizedAliasResolution is NOT used. The wording in the configuration (as shown in the OSGI Webconsole) should be adjusted too.

The removal of this code path should be considered as next step, taking place in 12+ months earliest.

Issue Links

• relates to: SLING-12025 ResourceResolver: different mapping when optimizedAliasResolution enabled
• links to: GitHub Pull Request #106