Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "JSDT/Debug/Rhino"

< JSDT‎ | Debug
(Local Rhino Debugging)
(Rhino Debug Wire Protocol)
 
(4 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
The bundles provided by JSDT debug for the Rhino support include:
 
The bundles provided by JSDT debug for the Rhino support include:
  
*<code>org.eclipse.wst.jsdt.debug.rhino</code> - the core Rhino implementation, provides the Rhino-specific implementation of [[JSDT/Debug/JavaScript Debug Interface|JSDI]]
+
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/plugins/org.eclipse.wst.jsdt.debug.rhino/?root=WebTools_Project org.eclipse.wst.jsdt.debug.rhino] - the core Rhino implementation, provides the Rhino-specific implementation of [[JSDT/Debug/JavaScript Debug Interface|JSDI]]
*<code>org.eclipse.wst.jsdt.debug.rhino.ui</code> - the Rhino-specific user interface bits
+
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/plugins/org.eclipse.wst.jsdt.debug.rhino.debugger/?root=WebTools_Project org.eclipse.wst.jsdt.debug.rhino.debugger] - the Rhino debugger that can be embedded in a server for remote debugging
*<code>org.eclipse.wst.jsdt.debug.rhino.debugger</code> - the Rhino debugger that can be embedded in a server for remote debugging
+
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/tests/org.eclipse.wst.jsdt.debug.rhino.tests/?root=WebTools_Project org.eclipse.wst.jsdt.debug.rhino.tests] - contains Rhino specific tests
 +
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/plugins/org.eclipse.wst.jsdt.debug.rhino.ui/?root=WebTools_Project org.eclipse.wst.jsdt.debug.rhino.ui] - the Rhino-specific user interface bits
  
 
== Local Rhino Debugging ==
 
== Local Rhino Debugging ==
Line 15: Line 16:
 
The related New and Noteworthy entry is [http://www.eclipse.org/webtools/development/news/3.3M2/sourceediting.php here].
 
The related New and Noteworthy entry is [http://www.eclipse.org/webtools/development/news/3.3M2/sourceediting.php here].
  
The details about using and setting up local Rhino debugging can be found on [[JSDT/Debug/Local Rhino Debugging|this page]].
+
The details about using and setting up local Rhino debugging can be found on [[JSDT/Debug/Rhino/Local Rhino Debugging|this page]].
  
 
== Embedding the Rhino Debugger ==
 
== Embedding the Rhino Debugger ==
Line 22: Line 23:
 
the Rhino Debugger allows you to remotely debug the loading and execution of scripts from the Eclipse IDE.
 
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 [[JSDT/Debug/Embedding_Rhino_Debugger|this page]].
+
To learn how to embed the Rhino Debugger please go to [[JSDT/Debug/Rhino/Embedding_Rhino_Debugger|this page]].
  
 
== Rhino Debug Console ==
 
== 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  
 
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. [[JSDT/Debug/Using_Rhino_Console|This page]] describes how to launch with the Rhino console and some common usage scenarios.
+
is loading scripts on demand. [[JSDT/Debug/Rhino/Using_Rhino_Console|This page]] describes how to launch with the Rhino console and some common usage scenarios.
  
 
== Rhino Debug Wire Protocol ==
 
== Rhino Debug Wire Protocol ==
Line 33: Line 34:
 
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.  
 
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 [[JSDT/Debug/Rhino_Debug_Wire_Protocol|RDWP]] can be found [[JSDT/Debug/Rhino_Debug_Wire_Protocol|here]].
+
The complete specification for the [[JSDT/Debug/Rhino/Rhino_Debug_Wire_Protocol|RDWP]] can be found [[JSDT/Debug/Rhino/Rhino_Debug_Wire_Protocol|here]].

Latest revision as of 21:44, 14 January 2011

JSDT Debug
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse SourceProject Set File

Overview

Support for the Rhino JavaScript interpreter is available in the JSDT feature and is provided to allow local and remote debugging of JavaScript using Rhino.

The bundles provided by JSDT debug for the Rhino support include:

Local Rhino Debugging

New to 1.3 is the ability to locally launch and debug JavaScript file(s) using Rhino. This new launching support includes context-sensitive launching from the platform and automatic source / script path updating.

The related New and Noteworthy entry is here.

The details about using and setting up local Rhino debugging can be found on this page.

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 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.

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.

Back to the top