You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/09/29 09:00:44 UTC

[jira] Closed: (SLING-680) Provide Web Console Plugin to list known ScriptEngines

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

Felix Meschberger closed SLING-680.
-----------------------------------

    Resolution: Fixed

Added a Web Console plugin Rev. 700001.

To implement the plugin, I also implemented a SlingScriptEngineManager, which helps registering ScriptEngineFactory instances and keeps track of them for display.

> Provide Web Console Plugin to list known ScriptEngines
> ------------------------------------------------------
>
>                 Key: SLING-680
>                 URL: https://issues.apache.org/jira/browse/SLING-680
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting Core 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Scripting Core 2.0.4
>
>
> By implementing SLING-636 the Scripting Core now logs the known script engines to the log file as they are encountered. As also noted in that issue, it would be helpful to have a Web Console plugin, which lists the known script engines.

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