[jira] Closed: (SLING-678) Enable Rhino debugger by framework property

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

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

Felix Meschberger closed SLING-678.
-----------------------------------

    Resolution: Fixed

Implemented this feature in Rev. 699373.

By setting the "org.apache.sling.scripting.javascript.debug" framework property (e.g. as a system property when launching the Sling or as a property in the sling.properties file) to "true", the debugger will be started whenever Rhino is called.

The debugger window will remain open until the RhinoScriptEngineFactory is stopped. If the window is closed by the user it is automatically reopened the next time an ECMAScript is run.

> Enable  Rhino debugger by framework property
> --------------------------------------------
>
>                 Key: SLING-678
>                 URL: https://issues.apache.org/jira/browse/SLING-678
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting JavaScript (Rhino)
>    Affects Versions: Scripting JavaScript 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For:  Scripting JavaScript 2.1.0
>
>
> Currently the server side Rhino debugger is enabled by placing a file in the /tmp directory (see SLING-193).
> This is not very appropriate and should be replaced by a framework property, which when set will enable the Rhino debugger.

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