Active Script debug limitations

HTML Script Application

You might experience the following problems when trying to launch an HTML Script Application debug session:

To correct these problems, complete the following steps:

When trying to attach to an existing browser for debug, do not attempt to attach to the WebSphere® Studio workbench internal browser. Attaching to the internal browser for debug will cause your workbench to stop responding and unexpected results might occur.

You might experience the following problems during an HTML Script Application debug session:

You can correct these problems by completing one of the following tasks:

Having the workbench Help window or internal browser opened during an Active Script debug session might interfere with the debug session and result in unexpected behavior. Some editors and views, like the Page Designer Editor and the Java™ Script Editor, have preview panes which also use the internal browser. Do not use these editors during an Active Script debug session - if they are used, do not open the preview pane.

Breakpoints set before a debug session are ignored if the page is deployed onto a server. To set a breakpoint, suspend the debug session to bring up the source and set the breakpoint at that temporary page. Refer to Setting a line breakpoint for details.

The Active Script debugger makes use of the Microsoft Script debugger to obtain debug information. For additional issues related to Microsoft Script debugger, refer to its ReadMe.htm.

Breakpoints can be added for a file with a *.js extension only if the file resides in the workspace. You cannot set breakpoints in *.js files if they do not reside in the workspace.

Breakpoints cannot be added for a file with a *.js extension if you have started the debug session by way of Debug on Server.

Script Host Application

You might experience the following problem when trying to launch a Script Host Application debug session:

You can correct this problem by doing the following:

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2005. All Rights Reserved.