[jira] Closed: (SLING-97) Script engines as plugins

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-97.
----------------------------------

    Resolution: Won't Fix

Closing this issue wontfix because we now use Java Scripting API for plugging in ScriptEngines and microsling is replaced by Launchpad based on full Sling with OSGi.

> Script engines as plugins
> -------------------------
>
>                 Key: SLING-97
>                 URL: https://issues.apache.org/jira/browse/SLING-97
>             Project: Sling
>          Issue Type: Improvement
>          Components: microsling
>            Reporter: Bertrand Delacretaz
>
> As discussed on sling-dev [1], a simple plugin mechanism should be used for ScriptEngines in microsling.
> I think the consensus is using a servlet init parameter to list the classnames of potential ScriptEngines, and only log a message if one cannot be implemented, without failing.
> People can then activate one of these engines by simply making its jar file available, or add any other engine providing they adapt the servlet init parameter value.
> Additional ScriptEngines (I think we agree to keep only the javascript/ESP one as standard) should probably move under sling-commons/script-engines, or under sling-scripting/script-engines if we have such a module (SLING-83).
> [1] http://thread.gmane.org/gmane.comp.apache.sling.devel/686/focus=732

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.