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 43659 - NPE while creating Project
Summary: NPE while creating Project
Status: CLOSED DUPLICATE of bug 41905
Alias: None
Product: platform
Classification: Unclassified
Component: Explorer (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Petr Nejedly
URL:
Keywords:
Depends on: 41691
Blocks:
  Show dependency tree
 
Reported: 2004-05-21 09:50 UTC by pfelenda
Modified: 2008-12-22 20:51 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Exception (5.47 KB, text/plain)
2004-05-21 09:51 UTC, pfelenda 		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 pfelenda 2004-05-21 09:50:28 UTC 
[refactoring 040529], jdk1.4.2_03
My steps:
- Create new Project (J2SE Application)
-> Exception appear

java.lang.NullPointerException
	at
org.netbeans.modules.java.ui.NavigationView.removeNotify(NavigationView.java:181)
	at
java.awt.Container.removeNotify(Container.java:2068)
Comment 1 pfelenda 2004-05-21 09:51:00 UTC 
Created attachment 15050 [details]
Exception
Comment 2 Lukas Hasik 2004-05-21 13:03:20 UTC 
happend in daily build [200405201800]
Comment 3 Tomas Hurka 2004-05-21 13:14:27 UTC 
Reassigning to java module.
Comment 4 Lukas Hasik 2004-05-21 13:26:55 UTC 
appers after any click on tab,etc..
the build is unusable because Editor is still empty/greyed -> P2
Comment 5 psuk 2004-05-24 11:02:33 UTC 
It happens to me also (randomly) since the floating windows were merged.

Was there a significant change in the way how winsys handle open/close
editor window?
Comment 6 psuk 2004-05-24 11:42:47 UTC 
The NPE happened on the same place in NB36 also. See Issue 41905.
Comment 7 Tomas Zezula 2004-06-30 14:16:17 UTC 
Seems that the ExplorerManager.find() returns null.
Not related to Java module.
Comment 8 Petr Nejedly 2004-07-07 08:05:35 UTC 
But EM.find is innocent here. I'd say the problem is in the
EM.Provider behind the scenes.
Can't reproduce the problem, so I won't tell you which EM.Provider is
wrong, but if you can reproduce it, just add a logging message to
EM whenever Provider passes null.

Whatever the wrong EM.Provider is, it is the same as in issue 41905

*** This issue has been marked as a duplicate of 41905 ***
Comment 9 pfelenda 2004-08-16 07:55:15 UTC 
Verified it is duplicate. There is the same Exception stack trace.