The IDE supports web module debugging, servlet debugging, and JSP debugging. Just as with Java programs, the IDE enables you to set new watches, evaluate a variable by holding the cursor over the variable, and set breakpoints in JSP files, JSP documents, and JSP segments.
The method that you use to start a debugging session depends on the type of component that you want to debug:
![]() |
When you change a JSP file while in a debugging session, you do not need to start a new debugging session. Just reload the page. |
The HTTP Monitor appears by default when you run web modules, JSP files, or servlets. The HTTP Monitor gathers data about HTTP requests that the servlet engine processes. For each HTTP request that the engine processes, the monitor records data about the incoming request, the data states maintained on the server, and the servlet context. You can view data, store data for future sessions, and replay and edit previous requests.
![]() |
To avoid getting JSP syntax-related errors when the server compiles a JSP file, right-click the JSP file and choose Validate from the contextual menu before you attempt to run the web module or the JSP page from the IDE. Note that the Validate action does not translate the JSP code into a servlet. Therefore, the Validate action does not discover syntax errors that occur at translation time or runtime. |
For help with the basic debugging tasks, see the Debugging Java Programs folder. The following list shows some of the Java program debugging topics that are helpful for debugging web modules:
Starting a Debugging Session Stepping Through Your Program Fixing and Continuing Breakpoints in the IDE Modifying Breakpoint Properties Variables and Expressions in the IDE |
See also | |
---|---|
Monitoring Data Flow on the Web Server Validating JSP Syntax Viewing a JSP's Servlet About JavaServer Pages Technology |