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.

Bug 167544 - debugger can't stop at the breakpoint when add some code into the jsp
Summary: debugger can't stop at the breakpoint when add some code into the jsp
Status: RESOLVED DUPLICATE of bug 167353
Alias: None
Product: javaee
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-23 16:06 UTC by difficult
Modified: 2009-11-13 03:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description difficult 2009-06-23 16:06:33 UTC
set a breakpoint on the jsp,and debug it,then add some code before the breakpoint.when debug again,the  programe hangs 
at the wrong location ,not at the breakpoint.
Comment 1 Petr Jiricka 2009-07-24 16:15:02 UTC
Hi, which server are you using? And which version/build of NetBeans? Thanks.
Comment 2 difficult 2009-07-26 07:37:00 UTC
my server include tomcat 5 ,tomcat6,GlassFish v2.1,GlassFish v3 Prelude and the version of NetBeans include from 6.01-
6.7.
I found it's nothing to do with the server,it my be the bug of NetBeans。
for example,in the jsp file have the following only scriptlet code.(the test entironment is Netbeans 6.7 and GlassFish 
v2.1)
<%
String s="test";
out.println(s);
%>
and I set the breakpoint at the line of "out.println(s)",and visit the jsp,the debugger stop at the right location.
then,I change the code as following,visit the jsp again.

<%
    String s = "test";
    int i=0;
    out.println(s);
    out.println(i);
%>
the debugger stop at the line of "out.println(i)" ,and can't evaluate the value of variable i.

if I restart the server,the debugger becomes rightly.  
Comment 3 Martin Entlicher 2009-11-13 03:50:22 UTC
Reproduced. This is actually a duplicate of bug #167353.
The changed code is deployed to the server, but debugger is not aware of that.

*** This bug has been marked as a duplicate of bug 167353 ***