[
https://issues.apache.org/jira/browse/SLING-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252484#comment-17252484
]
Konrad Windszus edited comment on SLING-10012 at 12/20/20, 6:16 PM:
--------------------------------------------------------------------
According to
https://github.com/apache/sling-org-apache-sling-servlets-resolver#so-how-do-i-deploy-my-scripts
I can put the scripts to src/main/scripts to precompile them. It seems that
HTL precompiled templates are not supported, so I have to put them to
src/main/resources/javax.script to make them discoverable (compare with
https://github.com/apache/sling-org-apache-sling-scripting-core/blob/ace78bd46a4eb2bfe41df15223294aef097a60e9/src/main/java/org/apache/sling/scripting/core/impl/bundled/BundleRenderUnitFinderImpl.java#L92).
If that is a general limitation and not a bug, this should be clearly
documented in
-
https://github.com/apache/sling-org-apache-sling-servlets-resolver#so-how-do-i-deploy-my-scripts
and
- https://github.com/apache/sling-scriptingbundle-maven-plugin
was (Author: kwin):
According to
https://github.com/apache/sling-org-apache-sling-servlets-resolver#so-how-do-i-deploy-my-scripts
in can put the scripts to src/main/scripts to precompile them. It seems that
HTL precompiled templates are not supported, so I have to put them to
src/main/resources/javax.script to make them discoverable (compare with
https://github.com/apache/sling-org-apache-sling-scripting-core/blob/ace78bd46a4eb2bfe41df15223294aef097a60e9/src/main/java/org/apache/sling/scripting/core/impl/bundled/BundleRenderUnitFinderImpl.java#L92).
If that is a general limitation and not a bug, this should be clearly
documented in
-
https://github.com/apache/sling-org-apache-sling-servlets-resolver#so-how-do-i-deploy-my-scripts
and
- https://github.com/apache/sling-scriptingbundle-maven-plugin
> Lookup of bundled template files does not work in some cases
> ------------------------------------------------------------
>
> 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
> 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 bundled 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)
