You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2008/01/24 19:00:46 UTC

[jira] Commented: (SLING-193) Rhino debugger for server-side javascript

    [ https://issues.apache.org/jira/browse/SLING-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562154#action_12562154 ] 

Bertrand Delacretaz commented on SLING-193:
-------------------------------------------

I have committed a first version in revision 614941, tested in the launchpad-webapp for simple cases.

The debugger is activated if the file /tmp/sling.debug exists when starting Sling (yes, a better configuration mechanism is a TODO ;-)

If the debugger is active, it should popup on the host that runs Sling, when running any server-side javascript.

I haven't checked what happens if running many scripts "simultaneously", but it seems to work fine to debug single scripts.

> Rhino debugger for server-side javascript
> -----------------------------------------
>
>                 Key: SLING-193
>                 URL: https://issues.apache.org/jira/browse/SLING-193
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> Integrate the Rhino debugger (http://www.mozilla.org/rhino/debugger.html), for server-side ESP and JS scripts

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