JSP Debugger FAQ

How does JspDebug work?

JspDebug compiles JSP files into Java files. This step is very similar to what an Application Server does with a JSP file, but JspDebug does this with a debugging orientation. The compiled Java file has a Java main program in it, and it can be run and debugged from an IDE like any other Java programs.

But my bug requires a full server environment!

JspDebug includes a debugging server. When you start your debugging session, the debugging server will listen on port 80 (or any other port number you specify) and will respond with HTML, GIF and other files, and will also handle servlets and filters as well as any JSPs other than the one(s) you are debugging. But when a JSP that you are debugging is invoked, your JSP class will be used, so you can use the IDE to set breakpoints etc.

Does JspDebug support a web-server?

Yes. You can specify a "web-server root", and for static files (such as HTML and GIF and JPEG files), it will look in the web-server root first.

What technology levels are provided?

JspDebug supports Servlet 2.3 and JSP 1.2 technologies.

Can I debug JSP 2.0 using JspDebug?

You will have to recode JSP 2.0 specific fragments using JSP 1.2, for instance using JSP expressions instead of EL expressions. Any tag libraries you are using must be JSP 1.2 compliant.

What limitations does the evaluation version have?

The evaluation version will generate Java files, but you will not be able to compile and/or run/debug it.

Can I debug multiple JSP files using JspDebug?

Yes, you can specify multiple JSP files. The first one that you specify will have the Java main program for debugging.