[
https://issues.apache.org/jira/browse/SLING-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olena updated SLING-10012:
--------------------------
Comment: was deleted
(was: The same scenario reproduces for the “data-sly-use”
- A resource type _page_ with a bundled script page.html contains
{code:java}
data-sly-use.head="head.html"{code}
- The extending resource type _myPage_ which has _page_ as resourceSuperType
contains head.html as a precompiled script file.
The same error on rendering the _myPage_:
{code:java}
Caused by: org.apache.sling.scripting.sightly.SightlyException: No use provider
could resolve identifier head.html at
org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension.call(UseRuntimeExtension.java:79)
[org.apache.sling.scripting.sightly:1.4.6.140] at
org.apache.sling.scripting.sightly.impl.engine.runtime.RenderContextImpl.call(RenderContextImpl.java:72)
[org.apache.sling.scripting.sightly:1.4.6.140] at
libs.core.wcm.components.page.v2.page.page__002e__html.render(page__002e__html.java:46)
[aem-precompiled-scripts:6.6.0.SNAPSHOT]
{code})
> Lookup of precompiled template files does not work
> --------------------------------------------------
>
> Key: SLING-10012
> URL: https://issues.apache.org/jira/browse/SLING-10012
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting HTL Engine 1.4.6-1.4.0
> Reporter: Konrad Windszus
> Assignee: Radu Cotescu
> Priority: Major
>
> I have a resource type {{a}} with a bundled script {{a.html}} which contains
> {code}
> <sly data-sly-use.simpleTemplate="simple.html"
> data-sly-call="${simpleTemplate.simple}"></sly>
> {code}
> I have an extended resource type {{myA}} which has {{a}} as
> resourceSuperType. That one contains {{simple.html}} as precompiled script
> file. Still the lookup when trying to render a resource based on {{myA}}
> fails with
> {code}
> Caused by: org.apache.sling.scripting.sightly.SightlyException: No use
> provider could resolve identifier simple.html
> at
> org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension.call(UseRuntimeExtension.java:79)
> [org.apache.sling.scripting.sightly:1.4.6.140]
> at
> org.apache.sling.scripting.sightly.impl.engine.runtime.RenderContextImpl.call(RenderContextImpl.java:72)
> [org.apache.sling.scripting.sightly:1.4.6.140]
> at
> org.apache.sling.scripting.sightly.<a>__002e__html.render(container__002e__html.java:62)
> {code}
> It works fine when trying to render a resource directly leveraging {{a}}, but
> in that case obviously the bundled {{a/simple.html}} is used
> Seems that the fix from SLING-9718 has not yet covered this use case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
