Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JSDT/Debug/Rhino"
(New page: == Single-click Launching == New to 1.3 is the ability to locally launch and debug JavaScript file(s) using Rhino. == Embedding the Rhino Debugger == One of the more powerful usages of th...) |
|||
Line 1: | Line 1: | ||
+ | {{JSDT-Debug}} | ||
+ | |||
== Single-click Launching == | == Single-click Launching == | ||
New to 1.3 is the ability to locally launch and debug JavaScript file(s) using Rhino. | New to 1.3 is the ability to locally launch and debug JavaScript file(s) using Rhino. |
Revision as of 14:48, 14 January 2011
JSDT Debug | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source • Project Set File |
Single-click Launching
New to 1.3 is the ability to locally launch and debug JavaScript file(s) using Rhino.
Embedding the Rhino Debugger
One of the more powerful usages of the Rhino debug support is that it can easily be embedded into your existing server. Embedding the Rhino Debugger allows you to remotely debug the loading and execution of scripts from the Eclipse IDE.
To learn how to embed the Rhino Debugger please go to this page.
Rhino Debug Wire Protocol
To provide support for the Rhino interpreter, we had to create both sides of the coin - the debugger and the client. To facilitate communication between the debugger and the client we created an adapted version of v8 (JSON-based) packet communication.