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.
I can't do anytyhing in my JSP editor without the following exception. It is quite frustrating. With every parse of the page it throws the error. Mon Jan 28 13:18:29 GMT 2002: java.lang.NoSuchMethodError: Posted StackTrace Annotation: Exception occurred in Request Processor org.openide.util.RequestProcessor$Holder: Posted StackTrace(task org.netbeans.modules.web.core.jsploader.TagLibParseSupport$ParsingRunnable@53a59 1 [-10, 1, -1]) at org.openide.util.RequestProcessor$Holder.fillInStackTrace (RequestProcessor.java:300) at java.lang.Throwable.<init>(Throwable.java:90) at java.lang.Exception.<init>(Exception.java:38) at org.openide.util.RequestProcessor$Holder.<init> (RequestProcessor.java:280) at org.openide.util.RequestProcessor$Task.createHolder (RequestProcessor.java:333) at org.openide.util.RequestProcessor.post(RequestProcessor.java:100) at org.openide.util.RequestProcessor.postRequest (RequestProcessor.java:185) at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.parseObject (TagLibParseSupport.java:111) at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.autoParse (TagLibParseSupport.java:88) at org.netbeans.modules.web.core.jsploader.BaseJspEditor$1.actionPerformed (BaseJspEditor.java:63) at javax.swing.Timer.fireActionPerformed(Timer.java:150) [catch] at javax.swing.Timer$DoPostEvent.run(Timer.java:108) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154) at java.awt.EventQueue.dispatchEvent(EventQueue.java:337) at java.awt.EventDispatchThread.pumpOneEventForHierarchy (EventDispatchThread.java:131) at java.awt.EventDispatchThread.pumpEventsForHierarchy (EventDispatchThread.java:98) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:85) Mon Jan 28 13:18:29 GMT 2002: java.lang.NoSuchMethodError: <no message> java.lang.NoSuchMethodError at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.parsePage (TagLibParseSupport.java:152) at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.access$200 (TagLibParseSupport.java:42) at org.netbeans.modules.web.core.jsploader.TagLibParseSupport$ParsingRunnable.run (TagLibParseSupport.java:120) at org.openide.util.Task.run(Task.java:152) [catch] at org.openide.util.RequestProcessor$ProcessorThread.run (RequestProcessor.java:622)
Created attachment 4453 [details] ide.log from the System folder
It looks like different version of ServletAPI (servlet.jar) on IDE classpath however the log doesn't show anything suspicious here. I am not sure what's the reason.
I've subsequently upgraded to v3.3.1 in an attempt to overcome this bug, but it's still there. I now also get bug #19831 whenever I try to get a contextual menu item on a JSP file tab within the Source Editor. This one is a critical error and asks me to submit it to the bug list. FYI: I have got Tomcat 3.2.4 and Tomcat 4.0 installed. I also have JBuilder5 and VisualAge for Java and all of these have hooks in to Tomcat and have a copy of servlet.jar within their directory structure. I also have a copy of servlet.jar (from Tomcat 4.0) used within a compile directory in the project I am currently working on. This directory contains files used when building the project using an Ant script. I can attach a new ide.log if you need it.
Mostly this is caused by different version of servlet.jar on a classpath (for example in JDK_HOME/jre/lib). Can it be the case? Don't you have Servlet2.3 installed?
For Info: I just upgraded to 3.3.1 from 3.3.0 and am hitting exceptions in the request processor all the time (clean all, compile all). I end up not even being able to close the IDE down: I have to kill the runide.exe process. Sadly I am backing off to previous version.
The problems with ServletAPI 2.2 vs 2.3 should be fixed in latest trunk builds. JSP parsing is separated from the rest of web module functionality here.
Verified with build 020318
Resolved for 3.4.x or earlier, no new info since then -> closing.