[SLING-9571] Nested selector scripts do not have a path-based registered servlet

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Servlets Resolver 2.7.0
• Fix Version/s: Servlets Resolver 2.7.2
• Component/s: Servlets
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 07/Jul/20 15:26
• Updated: 13/Jul/20 08:43
• Resolved: 07/Jul/20 15:46

Description

If a bundle provides a nested selector script (e.g. resourceType/selectorNesting/selectorScript.html) via the osgi.extender; osgi.extender="sling.scripting"; version:Version="1.0.0" capability of the org.apache.sling.servlets.resolver bundle, then the org.apache.sling.servlets.resolver.bundle.tracker.internal.BundledScriptTracker will not generate a path-based servlet, registering the selector combination only as part of a resource-type servlet. This will make script delegations (via sling:call, data-sly-include) fail.

Issue Links

• is related to: SLING-9207 Unify the support for bundled scripts