- XSLT Context View: If the node list is sorted, the XSLT Context view will show the node list in document order instead of the sorted order.
- XSLT Context and XSL Transformation Output views may not appear automatically when debug session is launched outside of the Debug perspective: Launching an XSL transformation debug session when not in the Debug perspective may cause the XSLT Context view and the XSL Transformation Output view not to appear. The views can be opened manually by choosing Window > Show View > Other from the workbench menu bar. In the Show View dialog, expand the Debug node and select the view that you want to open. Alternatively, you can correct this by terminating all debug launches and relaunching your application while in the Debug perspective. To prevent this from happening again, ensure that you are in the Debug perspective when launching a debug session.
- Erroneous JRE level warning dialog: The debugger may open an erroneous warning dialog about the JRE level when you launch an XSLT debug session. If you receive this dialog and you are using the product JRE (which you can check in the JRE tab of the launch configuration), you can ignore the message and click Yes in the dialog to launch the debug session.
- Source Not Found editor may close unexpectedly: In some cases, the debugger Source Not Found editor, which provides a button allowing you to edit the source lookup path, may close unexpectedly. To edit the source lookup path, right-click on an object in the Debug view and select Edit Source Lookup from the pop-up menu.
- Java communication timeout settings may need to be increased before performing a debug on server: If you are having trouble getting the debugger to connect to your application, you may need to increase your Java debug timeout settings. To determine if you are having this problem, check your
<workspace>\.metadata\.log
file for the existence oforg.eclipse.jdi.TimeoutException
messages. To increase the Java timeout settings, choose Window > Preferences from the workbench menu bar. Expand the Java node and click Debug. In the Debug preference page, increase both of the Communication timeouts (Debugger timeout (ms) and Launch timeout (ms) - it is recommended that you at least double the default values for these two fields). If the timeout settings are not increased, the debugger will appear to hang when you perform a debug on server.For applications running on WebSphere Application Server version 6.0, you may then attempt to reconnect by right-clicking the server in the Servers view, and selecting Reconnect debug process from the pop-up menu.
- JSP expression language is not supported: When debugging JSPs, EL (expression language) is not supported. For example, you cannot step into a JSP line that contains EL.
- 'Skip All Breakpoints' is not supported when debugging server-side JavaScript™: This action does not work for breakpoints that are set in server-side Javascript. When the action is enabled, breakpoints set in server-side JavaScript will be triggered.
- Debugging server-side JavaScript is not supported for WebSphere Application Server version 6.0: Server-side JavaScript debugging is only supported when debugging Web objects that are running on a WebSphere Application Server version 5.1.
- Compiled Language debugging views may not appear automatically when debug session is launched outside of the Debug perspective: Launching a compiled language debug session when not in the Debug perspective may cause some views to not appear. This includes the Registers, Memory, Memory Rendering, Monitors, and Modules views. The views can be opened manually by choosing Window > Show View > Other from the workbench menu bar. In the Show View dialog, expand the Debug node and select the view that you want to open. Alternatively, you can correct this by terminating all debug launches and relaunching your application while in the Debug perspective. To prevent this from happening again, ensure that you are in the Debug perspective when launching a debug session.
- Source editor may not highlight the current execution line: While debugging stored procedures, the source editor may not highlight the current execution line. To correct this, close the editor and then click on the top stack frame to reopen the editor.
Return to the main readme file