sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radu Cotescu (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-9571) Nested selector scripts do not have a path-based registered servlet
Date Tue, 07 Jul 2020 15:47:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Radu Cotescu resolved SLING-9571.
---------------------------------
    Resolution: Fixed

Fixed in [commit 208e935|https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/208e935].

> Nested selector scripts do not have a path-based registered servlet
> -------------------------------------------------------------------
>
>                 Key: SLING-9571
>                 URL: https://issues.apache.org/jira/browse/SLING-9571
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.7.0
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Servlets Resolver 2.7.2
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message