[rogue_dev]

Currently the JSP debugger establishes a virtual connection between the JSP source file (ie: test.jsp) and the Java code that the Web server is actually running (test.java -> test.class in the Web servers JSP working directory).

This works well for JSP files which do not include other JSP files or JSP fragments.

However, when the JSP file does include other files, there is a disparity between the JSP source files, the generated Java file (a composite of all the fragments) and the compiled class file. So if the debugger is showing that it is on line 4 in the JSP file, it may actually be on line 4 of the first included file. Trying to single step from a breakpoint often causes a run action.

So the request is for better integration between the debugger and the actual JSP file (or fragment) being debugged.

[Scott Anderson]

We’ve seen instances where stepping over/through includes matches up perfectly, and some where it does not and the difference is typically server dependent. For example, Tomcat and JBoss (since it uses Tomcat) and WebLogic 9 seem to do a great job. WebLogic 8.1 / Resin / others don’t do nearly as well. The reasons for the difference are in my last post in this thread:
http://www.myeclipseide.com/modules.php?op=modload&name=PNphpBB2&file=viewtopic&t=5033

[rogue_dev]

I just got it through my head what you meant in your linked post.

What I need to do is allow Tomcat to compile the JSP + fragments first, THEN set the breakpoints and step through the code.

If I set the breakpoint first (after a code change), then everything gets confused and the debugger gets “lost”. If I set it after the JSP compile, then it works.

This is on Tomcat 5.0.27

Thanks!

BTW, you guys do a great job dealing with the fragmented way we (the users) report problems. :-))

[Author]

Posts