You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/02/28 08:28:45 UTC

[jira] [Resolved] (SLING-3543) Provide a Felix Web Console Tab exposing the available Scripting Variables

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

Konrad Windszus resolved SLING-3543.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Scripting Core 2.0.46

Fixed by applying slightly modified patch leveraging JSONWriter from Felix Utils in [r1784700|http://svn.apache.org/r1784700].

> Provide a Felix Web Console Tab exposing the available Scripting Variables
> --------------------------------------------------------------------------
>
>                 Key: SLING-3543
>                 URL: https://issues.apache.org/jira/browse/SLING-3543
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: Scripting Core 2.0.26
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Scripting Core 2.0.46
>
>         Attachments: Scripting_Variables_Web_Console.png, SLING-3543-v01.patch
>
>
> Currently you can very dynamically define the scripting variables (https://cwiki.apache.org/confluence/display/SLING/Adding+New+Scripting+Variables). Therefore it would be very good to expose which variables are exposed within each script provider in a dedicated web console tab.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)