The IDE supports JSP debugging through enhancements to the standard debugging environment. These enhancements enable JSP and generated servlet files to be viewed simultaneously. Breakpoints set in one are automatically reflected in the other. However, breakpoints removed from the generated servlet are not removed from the corresponding JSP source file.
A JSP file, with all its included files, maps to a single servlet file. Specifically, one line in the JSP file maps to one or more lines in the servlet file. Some lines in the servlet file do not map to any single line in the JSP file.
In the IDE, you can call JSP compilation explicitly. To do this:
To debug a web module group:
Note that the HTTP Monitor appears by default when you are debugging JSP files. You can also use the HTTP Monitor without running the debugger. The HTTP Monitor gathers data about HTTP requests that are processed by the servlet engine. For each HTTP request that is processed, the monitor records data about the incoming request, the data states maintained on the server, and the servlet environment. You can view data, store data for future sessions, and replay and edit previous requests.
For help with standard debugging, see "Debugging a Program" in the Core IDE Help Set.
See also | |
---|---|
Setting JSP Debugger Options JavaServer Pages Technology Viewing Both JSP and Servlet Files During Debugging Monitoring Data Flow on the Web Server |