[
https://issues.apache.org/jira/browse/SLING-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282371#comment-14282371
]
Oliver Lietz commented on SLING-4330:
-------------------------------------
bq. Do I understand it correctly, that you propose to limit a ScriptEngine to
only handle scripts found at a certain location ?
Yes. I'm bringing an application to AEM 6 where different teams from different
companies work on the HTML templating in a round-trip manner. I had to disable
Sightly on AEM 6 as it always kicks in for scripts/templates with extension
{{.html}} and fails. This seems not to be a problem right now as Classic UI is
used for authoring and administration and JSPs besides Thymeleaf for
templating, but could (_will_) be a problem in the future of course. Ideally I
can configure Sightly to only handle scripts e.g. in {{/libs/foundation}} and
{{/apps/client/app2}}.
> provide a configuration parameter for paths patterns Sightly should handle
> --------------------------------------------------------------------------
>
> Key: SLING-4330
> URL: https://issues.apache.org/jira/browse/SLING-4330
> Project: Sling
> Issue Type: New Feature
> Components: Scripting
> Affects Versions: Scripting Sightly Engine 1.0.0
> Reporter: Oliver Lietz
>
> Running multiple script engines for same script (template) extension should
> be possible.
> Scripting Thymeleaf already provides that parameter, see
> {{org.apache.sling.scripting.thymeleaf.SlingTemplateModeHandler#getPatternSpec():org.thymeleaf.PatternSpec}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
