Skip to main content
Jump to: navigation, search

Difference between revisions of "JSDT/Debug"

Line 19: Line 19:
*'''org.eclipse.wst.jsdt.debug.rhino.tests''' - contains Rhino specific tests.
*'''org.eclipse.wst.jsdt.debug.rhino.tests''' - contains Rhino specific tests.
All of the bundles required for development of the JSDT debugger can be found [[Jsdt-debug.psf|here]].
All of the bundles required for development of the JSDT debugger can be found [[Media:Jsdt-debug.psf|here]].
== Planning ==  
== Planning ==  

Revision as of 12:10, 7 June 2010

JSDT Debug
Mailing ListForumsIRCmattermost
OpenHelp WantedBug Day
Browse SourceProject Set File

The JSDT debug project brings a variety of JavaScript debugging support to the JSDT using a common UI and communicating using a common protocol - JavaScript Debug Interface (JSDI). The common interface for the debugger emulates that of the platform and JDT debugger to allow a smooth transition and ease of use for the JSDT debugger.

Currently we have debugging support for Rhino and an incubation version of Crossfire / Firebug support.


The entire JSDT debugger is comprised of several bundles:

  • org.eclipse.wst.jsdt.debug.core - contains the JSDI specification and debug model elements.
  • org.eclipse.wst.jsdt.debug.crossfire (incubation) - contains a Crossfire implementation of the debugger.
  • org.eclipse.wst.jsdt.debug.rhino - contains a Rhino implementation of the debugger.
  • org.eclipse.wst.jsdt.debug.rhino.debugger - contains the Rhino debug hooks to connect to the Rhino interpreter.
  • org.eclipse.wst.jsdt.debug.ui - contains the shared UI presentation for the debugger implementations.
  • org.eclipse.wst.jsdt.debug.core.tests - contains related test cases for the debug core.
  • org.eclipse.wst.jsdt.debug.rhino.tests - contains Rhino specific tests.

All of the bundles required for development of the JSDT debugger can be found here.


JSDT Debug follows directly the project plan for JSDT.


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. The complete specification for the RDWP can be found here.

JavaScript Debug Interface (JSDI)

The JSDI is used to provide a common way for our models and UI to communicate with a variety of debugger back-ends - write one UI + model and provide additional debuggers. The complete specification for the JSDI can be found here.

Embedding the Rhino Debugger

To use the Rhino debug support it must be linked to a running Rhino interpreter. This page describes how to do this.

Using the Rhino Debug Console

Launching the Rhino debugger with the Rhino console available is a very powerful tool that allows developers to perform many operations, one notable operation is loading scripts on demand. This page describes how to launch with the Rhino console and some common usage scenarios.


Smoke Tests, scenarios, example scripts and more to aid testing.

Back to the top