[jira] [Resolved] (SLING-7290) The Sling Servlet Resolver does not work correctly in some inheritance scenarios

["Radu Cotescu (JIRA)" <ji...@apache.org>]

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

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

Pushed fix in [8246d7f|https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/8246d7fc1704202c63f2162a2c5b945a1701ce21].

> The Sling Servlet Resolver does not work correctly in some inheritance scenarios
> --------------------------------------------------------------------------------
>
>                 Key: SLING-7290
>                 URL: https://issues.apache.org/jira/browse/SLING-7290
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.4.20
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>             Fix For: Servlets Resolver 2.4.22
>
>
> Given the following script structure:
> {noformat}
> /libs/test
>     test.jsp
> /apps/test
>     test.html
> /apps/test2
>     [sling:resourceSuperType='test']
>     test2.jsp
> {noformat}
> Assuming there's a content resource at {{/content/test}} with a {{resourceType}} set to {{test2}}, the current servlet resolution from {{org.apache.sling.servlets.resolver}} 2.4.20 will pick the {{test.html}} script instead of the {{test2.jsp}} script, due to the fact that the HTL Script Engine Factory has a higher priority than the JSP Script Engine Factory.
> The Script Engine Factory priority should only be taken in consideration for scripts in the same folder.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)