Use JSP breakpoints (WebSphere Application Server debug)

A breakpoint causes the execution of a thread to suspend at the location where the breakpoint is set, only if the breakpoint is set on a debuggable line in the JSP. The following are considered debuggable JSP:

scriptlets (<% ... %>)
JSP expressions (<%= ... %>)
JSP declarations (<%! ... %>)
<jsp:include ... /> tags
<jsp:useBean /> tags
custom tags

A list of all breakpoints (for all debug sessions) appears in the Breakpoints view, unless you use the filter by debug target action. To filter out breakpoints that are not related to the current debug session, click the Breakpoints view Show Breakpoints Supported by Selected Target push button or right-click in the view and enable the Show Supported Breakpoints pop-up menu item (this menu item is enabled when you select it so that there is a check mark to the left of it).

Note: Filtering by debug target does not filter out breakpoints for debug targets that are similar to that of the current debug session.

Breakpoints can be enabled and disabled via their pop-up menus in the Breakpoints view. When a breakpoint is enabled, it will cause a thread to suspend whenever it is hit. When a breakpoint is disabled, it will not cause threads to suspend. For further information about enabling and disabling breakpoints, see the related topic below.

Line breakpoint indicators are displayed in the marker bar in the editor area and in a list in the Breakpoints view. The breakpoint entries in the list provide you, in brackets, with a summary of the breakpoints' properties. Pop-up menu options and push buttons in the Breakpoints view allow you to remove breakpoints.

While in the Breakpoints view, the source editor will open to the location of a breakpoint if you do one of the following:

Double-click the breakpoint.
Select the breakpoint and click the Go to File For Breakpoint push button.
Right-click on the breakpoint and select Go to File from the pop-up menu.

Use JSP breakpoints

Related tasks