You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2017/03/24 15:24:41 UTC
[jira] [Resolved] (SLING-6680) contributing esx scripting engine
[ https://issues.apache.org/jira/browse/SLING-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-6680.
----------------------------------------
Resolution: Fixed
Thanks for your contribution! I have committed it under contrib/scripting/esx and made minor changes in http://svn.apache.org/r1788469 and http://svn.apache.org/r1788470
It would be good to have integration tests, the Sling Pax Exam mechanism as used in bundles/extensions/org.apache.sling.resource.presence can be good for that.
I think we should consider this module experimental for now but it's good to have it IMO, I especially like the ability to use existing NodeJS modules.
> contributing esx scripting engine
> ---------------------------------
>
> Key: SLING-6680
> URL: https://issues.apache.org/jira/browse/SLING-6680
> Project: Sling
> Issue Type: New Feature
> Components: Scripting
> Reporter: Senol Tas
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: Apache Sling Scripting ESX 0.2.0
>
> Attachments: esx.zip
>
>
> I'd like to contribute a small scripting engine which is using a nodejs like module loading.
> This module implements a Nashorn Apache Sling Script Engine for the "esx" extension.
> It requires a function named render in the esx script that processes the request.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)