[jira] [Commented] (SLING-7151) Resources with relative paths aren't being resolved correctly for overlays

["Robert Munteanu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179167#comment-16179167 ] 

Robert Munteanu commented on SLING-7151:
----------------------------------------

I've deleted the parsys.jsp file as I believe it does not belong here based on the license header:

{noformat}This software is the confidential and proprietary information of
  Day Management AG, ("Confidential Information"){noformat}

Can you please attach a reproducible case that works on top of Sling?

> Resources with relative paths aren't being resolved correctly for overlays
> --------------------------------------------------------------------------
>
>                 Key: SLING-7151
>                 URL: https://issues.apache.org/jira/browse/SLING-7151
>             Project: Sling
>          Issue Type: Bug
>         Environment: AEM 6.3
>            Reporter: Marcus Hicks
>            Priority: Critical
>         Attachments: apps_parsys_overlay.PNG, libs_parsys_overlay.PNG
>
>
> Our parsys overlay at /apps/foundation/components/parsys isn't working in AEM 6.3 due to an issue with the way sling is resolving relative paths for resources.
> The error occurs in parsys.jsp at line 120 when the 'new' resource is embedded using the cq:include tag. The path being used to resolve the 'new' resource is foundation/components/parsys/new. Based off the default configuration in the Apache Sling Resource Resolver Factory OSGI config, the expected behavior is for sling to check for the resource under /apps, and if it's not there then search under /libs. The problem seems to be that sling is ignoring the default configuration and not doing subsequent searches for relative paths when it doesn't find the resource under /apps.
> As discussed in this [post|https://forums.adobe.com/thread/2332745], the workaround to fix the particular incident with the parsys is to copy the 'new' node from /libs/foundation/components/parsys to our overlay under /apps. However, this doesn't solve the overarching issue of sling not resolving the relative path correctly which could impact other parts of the site where we're including resources on pages using relative paths.
> I've attached the code for parsys.jsp as well as screenshots of our overlay under /apps and the original component under /libs.



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