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 138173 - NullPointerException at java.util.StringTokenizer.<init>
Summary: NullPointerException at java.util.StringTokenizer.<init>
Status: RESOLVED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Templates (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: rmichalsky
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-25 03:28 UTC by daveyost
Modified: 2008-07-08 14:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 69208

Attachments
stacktrace (6.48 KB, text/plain)
2008-06-25 03:29 UTC, daveyost 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description daveyost 2008-06-25 03:28:54 UTC 
Build: NetBeans IDE Dev (Build 200806231203)
VM: Java HotSpot(TM) Client VM, 1.5.0_13-119, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_13-b05-237
OS: Mac OS X, 10.5.3, i386

User Comments: 
Trying to create an xml file type
Comment 1 daveyost 2008-06-25 03:29:09 UTC 
Created attachment 63385 [details]
stacktrace
Comment 2 rmichalsky 2008-07-02 17:09:06 UTC 
Fixed in core-main. changeset 87401	d66660a1ff01
Generation of data object test (temporarily?) disabled for XML-based data loaders, problems with test setup (no public
API for XML resolver).
Comment 3 Jesse Glick 2008-07-02 18:00:48 UTC 
See issue #138846.

BTW please set the Target Milestone whenever resolving an issue as FIXED.
Comment 4 Quality Engineering 2008-07-03 04:31:42 UTC 
Integrated into 'main-golden', available in NB_Trunk_Production #296 build
Changeset: http://hg.netbeans.org/main/rev/d66660a1ff01
User: Richard Michalsky <rmichalsky@netbeans.org>
Log: #138173: Fixing NPE in New File Type Wizard
Comment 5 rmichalsky 2008-07-04 13:29:56 UTC 
ad #138846: in my case the missing part was an API for creating an instance of MIMEResolver for given XML resolver
definition. Except for that everything else was a matter of correct lookup setting.

ad milestone: sorry again, I keep forgetting that :).
Comment 6 Jesse Glick 2008-07-08 14:28:19 UTC 
As of issue #138846, the current unit test generation is wrong. I filed issue #139253.