[jira] [Updated] (SLING-11373) The MergingServletResourceProvider does not wrap resources correctly

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

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

Radu Cotescu updated SLING-11373:
---------------------------------
    Summary: The MergingServletResourceProvider does not wrap resources correctly  (was: The MergingServletResourceProvider does not correctly wrap resources)

> The MergingServletResourceProvider does not wrap resources correctly
> --------------------------------------------------------------------
>
>                 Key: SLING-11373
>                 URL: https://issues.apache.org/jira/browse/SLING-11373
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.7.0
>            Reporter: Radu Cotescu
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: Servlets Resolver 2.9.8
>
>
> The {{MergingServletResourceProvider}} does not wrap resources correctly, forcing script engines that need to solve dependencies via this provider to call {{ResourceResolver#resolve(String)}}. Unfortunately, there is a case when the call to {{resolve}} fails:
> {noformat}
> /apps/components/a/
>     a.html
>     helper.something.html
>     helper/ [backed by JCR]
>       partial.html
> /apps/components/b [sling:resourceSuperType=components/a]
>     b.html -> tries to resolve helper.something.html
> {noformat}
> In the case above, {{b.html}} will get the {{helper}} folder when trying to resolve {{helper.something.html}}.
> If the {{MergingServletResourceProvider}} would correctly wrap resources (and decorate them accordingly), the script engines could switch to using {{ResourceResolver#getResource(String)}}, which would not exhibit the same behaviour.
>     



--
This message was sent by Atlassian Jira
(v8.20.7#820007)