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.
[Build 200407271830, JDK 1.5.0] Add following three lines to JSP: aaa 1 + 2 = ${1 + 2} <br> bbb Put a breakpoint to first line and start debugger. When the breakpoint is reached, move mouse over ${1 + 2} to show tooltip evaluation. Then press F8. Next line of JSP ins't reached and debugger session is now broken.
I was not able to reproduce on 1.4.2_05. Sucessfuly reproduced on 1.5.0-beta2. Reassigning to debuggerjpda for deeper look. Evaluation of EL expression ${1+2} means evaluation of a statement (aka hidden watch) below in the context of a jsp: pageContext().getExpressionEvaluator().evaluate("${1+2}", java.lang.String.class, (javax.servlet.jsp.PageContext)pageContext, null) and from the behaviour it seems like the debugger gets into running state while evaluating the expression.
I can confirm that it's JDK1.5 specific.
I can reproduce it on 1.5.0-b61. Debugee stops (for unknown reason) at org.apache.jasper.runtime.HttpJspBase.service:95 at which point debugger resumes it with smart stepping because no sources are available. More research is needed (may be JDK build-specific?). No problems with JDK 1.4.2.
Looks like some bug in JDK.
Reproducible on JDK 1.5.0 FCS. Looks like to same root cause as in 49576.
What's the bug number of JDK issue then? This is a serious issue (P2), I believe you will not be able to waive it by saying 'this is jdk bug'. I just noticed that Jarda's issue is a P1!
*** This issue has been marked as a duplicate of 50315 ***
The bug which this bug is duplicate of is RESOLVED-WONTFIX, but I can't agree with this solution. As user I don't care whether the bug is in the IDE or JDK. And the JDK bug will not be likely fixed in JDK1.5.0_01. Is there any possibility to implement some workaround?
No known workarround on JDK1.5.0. You can use JDK1.4.x. *** This issue has been marked as a duplicate of 50315 ***
Sorry, I forgot to change component. I meant workaround in webapps code.
We may disable EL evaluation for 1.5 if that's what you would call a workaround, but then this will never work in 4.0+jdk1.5 even when the bug is fixed in later releases of jdk. Let me know what you think. No other workaround known. The only thing we can do is release note this and push jdk team to fix the bug (I adjusted priority of the bug already).
I have probably found some workarround, which is not so painful. The bug occurres during evaluation of expression loading a new instances of classes. Checking in src/org/netbeans/modules/debugger/jpda/expr/Evaluator.java; /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/expr/Evaluator.java,v <-- Evaluator.java new revision: 1.13; previous revision: 1.12 done
Works fine for me.
verified in 200410311900
verified