[
https://issues.apache.org/jira/browse/SLING-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-636.
---------------------------------------
Resolution: Fixed
In revision 690922, script extension mapping info is logged at the INFO level
for each extension found in any valid ScriptEngine provided by a bundle or
service.
This happens every time the ScriptEngineManager is reinitialized, for example
if a new bundle with a META-INF/services/javax.script.ScriptEngineFactory entry.
Note that the ScriptEngineManager is initialized on demand, when a ScriptEngine
needs to be found for a script, so after installing a new ScriptEngine bundle
one needs to make a request that uses a script (for example request
content/foo/*.html and put a script a /apps/foo/foo.xyz) to see those log
messages.
Example log message:
Script extension 'ecma' is now handled by
ScriptEngine 'Sling - Scripting - JavaScript Support (Rhino 1.6 release 6 2007
07 26)',
version='2.0.3-incubator-SNAPSHOT',
class='org.apache.sling.scripting.javascript.RhinoJavaScriptEngine'
> Log more info about script engine extension mappings
> ----------------------------------------------------
>
> Key: SLING-636
> URL: https://issues.apache.org/jira/browse/SLING-636
> Project: Sling
> Issue Type: Improvement
> Affects Versions: Scripting Core 2.0.2
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Fix For: Scripting Core 2.0.4
>
>
> Logging exactly which script extensions are handled by which ScriptEngine
> would help troubleshooting new ScriptEngines.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
