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: | step into a tag handler in JSP page doesn't work | ||
---|---|---|---|
Product: | javaee | Reporter: | Jindrich Sedek <jsedek> |
Component: | Debugger | Assignee: | Martin Entlicher <mentlicher> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | mentlicher, mfukala, pjiricka |
Priority: | P3 | Keywords: | REGRESSION |
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Application that reproduces this bug
Stack trace |
Description
Jindrich Sedek
2009-04-09 12:22:17 UTC
this is regression - it worked better in 6.5.1 - I need to press Step Into for few times to navigate to my code, but at least no other files from JDK got opened Martin, any idea what could be wrong? Thanks. Created attachment 80221 [details]
Application that reproduces this bug
I am able to reproduce (with GlassFish v2.1 as the target server). I attached the application that reproduces the issue. When I try Shift-F7, there is an exception, see attached. Created attachment 80263 [details]
Stack trace
The attached exception is already submitted as issue #162740. I'll try to reproduce and hopefully find out what's wrong... I've reproduced the behavior. This is mostly caused by enabled stepping into JDK classes, which is now on by default. Stepping filters should help here, ClassLoader is correctly skipped, but it looks like the "Step through" option is not correctly interpretted and execution ends up in Logger. Also, the first Step Into goes into the same location, but in the next frame. It looks like nothing has happened, but execution actually stepped into in the Java code that is underneath. Is it possible to see the generated Java code somewhere? If you mean generated code of JSP page, use ViewServlet action on JSP file Yes, thanks. View Servlet was what I need. Having that on a context menu in Editor would be handy. I believe that the major problem was fixed in changeset: 127653:d638dc946f45 http://hg.netbeans.org/main/rev/d638dc946f45 You should not end up in JDK code now. However, the behavior is still not perfect, first Step Into ends up on the same line, second goes to the non-existent constructor and finally third goes into the doTag() method. This is a subject of further investigation... Integrated into 'main-golden', will be available in build *200904180201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/d638dc946f45 User: mentlicher@netbeans.org Log: #162293 - Stepping options are better interpretted, handling of step requests improved. Integrated into 'main-golden', will be available in build *200904201507* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/d638dc946f45 User: mentlicher@netbeans.org Log: #162293 - Stepping options are better interpretted, handling of step requests improved. Is this still P2 after the fix? I tend to downgrade it to P3 now. Jindro, can you please verify it? Thanks. I can verify that the behavior is better than before. Once I was redirected into Class.java file for unknown reason, but it could be threated as P3 for 6.7 After agreement with QE and mentlicher downgrading to P3. 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 |