This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | DEBUG: "step out", "step in", "step over" not as clear in JSP as in java code | ||
|---|---|---|---|
| Product: | javaee | Reporter: | Jason Rush <jrush> |
| Component: | Debugger | Assignee: | Martin Entlicher <mentlicher> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | CC: | jskrivanek |
| Priority: | P3 | ||
| Version: | 4.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
|
Description
Jason Rush
2003-02-16 18:50:36 UTC
Transferred from BugTraq 4389763. Discussed this with Jeff Hoffman today. We think that the desirable behaviour here would be: Step into: - If you are on a request dispatcher statement <jsp:forward> or <jsp:include>, then this should cause the debugger to stop on the first line of code in the included file - If you are on a line that indicates a static include, go to the first line in the included file - If you are on a custom action, try to step into the relevant tag handler method. - If you are in a scriptlet or similar with a java method invocation on another object, same as a java class. If we can't implement the first two, it might be better to disable the step into action? Step out: - If in a JSP that was dispatched to (included or forwarded) run to the end of the JSP and stop on the servlet or JSP that forwarded to it and stop on the next line of code in that file (or run to end if this object handled the incoming request. - If in a JSP that was statically included (includes prelude or coda), go to the first line of code in the including file after the include statement. For a coda, this means to the same as for a dynamic include since there are no more lines in the JSP itself. - If you're in a tag handler or other java object invoked from a JSP, you should end up in the JSP. Step over should go to the next line in the current source, that one should be trivial with JSR-45. Almost all of these work now. The only remaining problems are static includes - Step Over and Step Out does not work as expected. Status is: Step In - steps into include Step Over - steps into include Step Out - steps out of the whole jsp itself This will need to be fixed by some hidden breakpoints, or some advanced stepping filtering. Will see whether we'll have time to fix these to promo-D. *** Issue 40428 has been marked as a duplicate of this issue. *** Previously targeted for 4.0, so hopefully will be fixed in 4.1. Not as easy as it looks. JSR-45 solved many things but on the other hand it cannot solve the remaining. Generally, the problem is that the actins like step over/into are in fact performed on Java source, not on JSP. JSR-45 then translates the Java lines into JSP lines and we cannot easily decide whether to continue or not. e.g., JSP parser should be involved in solving this issue. It will be done hopefully in the next version. This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss |