[SLING-8110] Take extensions, selectors etc. into account for selecting path-mounted servlets

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Servlets Resolver 2.6.0
• Component/s: Servlets
• Assignee: Bertrand Delacretaz
• Reporter: Bertrand Delacretaz
• Created: 15/Nov/18 12:38
• Updated: 10/Mar/20 07:40
• Resolved: 06/Mar/20 10:43

Description

If a Sling Servlet has both paths and extensions service properties, currently the paths take over and the extensions are ignored.

This has caused confusion with users who have set both properties on a servlet - my initial thought was to reject such illegal combinations, but a colleague rightly notes that it would make sense to honor the extensions property as well, and only route requests to that servlet if there's a match on the extension.

This requires more analysis, for now I'm just creating this ticket to remind us to have another look.

Issue Links

• causes: SLING-9164 NPE when resolving servlets for resource types
• is blocked by: SLING-8936 Improve test coverage for path-mounted servlets
• is related to: SLING-9055 Implement a new SlingServletPathsStrict annotation
• is related to: SLING-9176 Document sling.servlet.paths.strict and corresponding behavior