[
https://issues.apache.org/jira/browse/SLING-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990410#comment-13990410
]
Bertrand Delacretaz commented on SLING-3543:
--------------------------------------------
Indeed, it seems hard to get reliable info just by looking at the services.
The simplest might be to use a service property with a specific name
("bvp.info" maybe) that each BVP can supply to explain what it expects and what
it provides. We can then add that property to the Sling BVPs, and your console
plugin can complain for those that don't supply the bvp.info property. That's
not ideal as there's no way to make sure the value of that property is in sync
with the actual code, but the only reliable alternative that I see is to
execute actual Sling requests and check what variables are added by each BVP,
for various languages, which is a bit complicated.
> 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
>
> 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.2#6252)
