[SLING-10012] Lookup of precompiled template files does not work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Scripting HTL Engine 1.4.6-1.4.0
• Fix Version/s: Scripting HTL Engine 1.4.8-1.4.0, Scripting HTL Testing Content 1.0.28-1.4.0, Scripting HTL Testing 1.0.30-1.4.0
• Component/s: Scripting
• Assignee: Radu Cotescu
• Reporter: Konrad Windszus
• Created: 18/Dec/20 18:20
• Updated: 11/May/21 13:01
• Resolved: 04/Mar/21 14:36

Description

I have a resource type a with a bundled script a.html which contains

<sly data-sly-use.simpleTemplate="simple.html"
       data-sly-call="${simpleTemplate.simple}"></sly>

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

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)

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.

Issue Links

• is blocked by: SLING-9999 Remove cyclic dependency between scripting and servlets features
• is blocked by: SLING-10185 Allow a ServletResource to adapt to a BundledRenderUnit
• relates to: SLING-9718 Relative paths for bundled HTL template files are not correctly handled
• links to: GitHub Pull Request #1