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 120760 - NullPointerException at org.netbeans.modules.web.jspparser.JspParserImpl.initReflection
Summary: NullPointerException at org.netbeans.modules.web.jspparser.JspParserImpl.init...
Status: VERIFIED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP Parser (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Tomas Mysik
URL: http://statistics.netbeans.org/except...
Keywords:
: 120740 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-11-01 08:20 UTC by Jiri Skrivanek
Modified: 2009-05-25 14:03 UTC (History)
19 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 4263


Attachments
stacktrace (711 bytes, text/plain)
2007-11-01 08:20 UTC, Jiri Skrivanek
Details
stacktrace (711 bytes, text/plain)
2007-11-01 10:27 UTC, Max Sauer
Details
stacktrace (711 bytes, text/plain)
2007-11-01 11:37 UTC, Miloslav Metelka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2007-11-01 08:20:42 UTC
Build: NetBeans IDE Dev (Build 20071101044337)
VM: Java HotSpot(TM) Client VM, 1.6.0_03-b02
OS: Windows XP, 5.1, x86

User Comments: 
It started happen in build #4234 and it also breaks UI validation tests. Probably caused by psuchomel commit:

http://deadlock.netbeans.org/hudson/job/trunk/4234/changes#detail2

To reproduce just create a web project. When a JSP is opened the excetpion is thrown.
Comment 1 Jiri Skrivanek 2007-11-01 08:20:50 UTC
Created attachment 52217 [details]
stacktrace
Comment 2 Martin Schovanek 2007-11-01 09:24:15 UTC
*** Issue 120740 has been marked as a duplicate of this issue. ***
Comment 3 Max Sauer 2007-11-01 10:27:21 UTC
Build: NetBeans IDE Dev (Build 20071101060911)
VM: Java HotSpot(TM) Client VM, 1.5.0_12-b04
OS: SunOS, 5.10, sparc

User Comments: 
Created a new WebApplication type project, right after startup in a new userdir. (IDE opened welcomeJSF).
Comment 4 Max Sauer 2007-11-01 10:27:28 UTC
Created attachment 52227 [details]
stacktrace
Comment 5 Petr Suchomel 2007-11-01 10:43:09 UTC
This definitely seems to be caused by me. If there is reflection call, I am having difficulties to find it.
Comment 6 Petr Suchomel 2007-11-01 10:54:08 UTC
Should be fixed now.

$ cvs -z6 -q ci -m "Fix for #120760 NullPointerException at org.netbeans.modules.web.jspparser.JspParserImpl.initReflection"
Checking in src/org/netbeans/modules/web/jspparser/JspParserImpl.java;
/cvs/web/jspparser/src/org/netbeans/modules/web/jspparser/JspParserImpl.java,v  <--  JspParserImpl.java
new revision: 1.39; previous revision: 1.38
done
Comment 7 Miloslav Metelka 2007-11-01 11:37:12 UTC
Build: NetBeans IDE Dev (Build 071101)
VM: Java HotSpot(TM) Client VM, 1.6.0_03-b04
OS: Linux, 2.6.20-16-generic, i386

User Comments: 
When creating a new web project or when creating a new jsp from template.
Comment 8 Miloslav Metelka 2007-11-01 11:37:16 UTC
Created attachment 52239 [details]
stacktrace
Comment 9 Jiri Skrivanek 2007-11-01 14:08:03 UTC
Verified.
Comment 10 tomashelgi 2008-10-05 15:00:24 UTC
Reopening - reproduced in NetBeans IDE 6.1 (Build 200805300101)
Comment 11 tomashelgi 2008-10-05 15:01:16 UTC
Reopening - reproduced in NetBeans IDE 6.1 (Build 200805300101)
Comment 12 Tomas Mysik 2008-10-06 10:24:58 UTC
To tomashelgi: could you please have a look at issue #146394? I think that it could be the right issue for your case. 
Thanks.

I'm not able to reproduce this issue - I tried to create a new Web application with JSF framework - welcomeJSF.jsp 
page is opened, no error occured. If you are still able to reproduce this issue using the latest development build or 
if my scenario is incorrect, please reopen. Thanks.

Product Version: NetBeans IDE Dev (Build 081006)
Java: 1.5.0_16; Java HotSpot(TM) Client VM 1.5.0_16-b02
System: Linux version 2.6.26-gentoo-r1 running on i386; UTF-8; cs_CZ (nb)
Comment 13 Jiri Skrivanek 2008-10-06 10:47:31 UTC
Verified. It was false alarm of the exception reporter - not 6.1 but 6.5 and stack trace is also little bit different
than the original one.