|Mailing List • Forums • IRC|
|Browse Source • Project Set File|
This page contains a collection of common questions and answers and common problems and possible solutions.
Check back often, new content will be added regularly.
Where is the Source?
Depending on the version of JSDT you have installed, locating the remote source in your workspace can be a bit tricky.
Pre 1.3.x External Source
Realizing that this source story was sub-optimal we sat down and completely re-designed it to be more user friendly.
1.3.x External Source
To combat the non-user-friendly source story from pre-1.3.x JSDT we made the following major changes:
http://www.mozilla.com/js/jquery/jquery.min.jswould be saved in the project like:
Getting Source Lookup to work
This bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=328531 causes the source lookup to fail for various reasons. There is a workaround for this problem.
- When compiling/interpreting your script in Rhino there's a 'scriptName' parameter that you supply. To make the source lookup find your source this parameter must equal the full path to your script's source.
- In the client (Eclipse), in the debug configuration screen for your Rhino remote debugger go to the "Source" tab, and Add the project where your script's source resides.
- To make sure the process worked, connect to the debugger, and try to set a breakpoint in Eclipse. If you see in the transport (prints to STDOUT assuming the debugger was initialized with "trace=y") a "setbreakpoint" request, that means the client was able to attach the local source to the one running in Rhino.
Can I See Loaded Scripts?
To view what scripts have been loaded in the VM simple use the 'Show All Scripts' action in the Debug view.
Activating this action will place a 'Scripts' node in the tree, which contains all of the scripts currently loaded in the VM.