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

Konrad Windszus commented on SLING-4330:
----------------------------------------

For the record: Fixed via 
https://github.com/apache/sling-org-apache-sling-scripting-core/commit/09e48f47691dbb1825e74c44f1f2bb6df9c9eb78
 and 
https://github.com/apache/sling-org-apache-sling-scripting-core/commit/9f6efcc30342736cb02895ad40558920c79ce2c0
[~olli] Can you add some documentation at 
https://sling.apache.org/documentation/bundles/scripting.html?

> Select script engines in SlingScriptAdapterFactory via mapping
> --------------------------------------------------------------
>
>                 Key: SLING-4330
>                 URL: https://issues.apache.org/jira/browse/SLING-4330
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting Core 2.0.28
>            Reporter: Oliver Lietz
>            Assignee: Oliver Lietz
>            Priority: Major
>             Fix For: Scripting Core 2.0.60
>
>
> 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}}.-
> Support for multiple script engines via mapping:
> {noformat}
> {
>   "sling:scripting": [
>     "html=The HTL Templating Language:1.4",
>     "js=ECMAScript:partial ECMAScript 2015 support"
>   ]
> }
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to