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 110101 - NPE in JFileChooser
Summary: NPE in JFileChooser
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: David Simonek
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2007-07-18 08:34 UTC by vtec
Modified: 2008-12-22 13:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
NPE from JFileChooser (5.74 KB, text/plain)
2007-07-18 08:38 UTC, vtec 		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 vtec 2007-07-18 08:34:44 UTC 
May be a JDK bug but also may be a result of some later netbeans customizations. While searching for a jar-file to be
added into project's classpath using JFileChooser popped out by "Add Jar/Folder" button I received nasty NPE from
JFileChooser. 

java.lang.NullPointerException
	at javax.swing.JComponent.repaint(JComponent.java:4746)
	at sun.swing.FilePane$2.repaintListSelection(FilePane.java:114)
	at sun.swing.FilePane$2.repaintSelection(FilePane.java:104)
	at sun.swing.FilePane$2.focusLost(FilePane.java:99)
	.... for complete stack-trace check attachment

Product Version: NetBeans IDE Dev (Build 200707171200) 
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 
System: Windows XP version 5.1 running on x86; Cp1252; en_GB (nb) 
Userdir: C:\Documents and Settings\developer\.netbeans\dev
Comment 1 vtec 2007-07-18 08:38:18 UTC 
Created attachment 45285 [details]
NPE from JFileChooser
Comment 2 Jan Chalupa 2007-07-18 14:55:40 UTC 
Really looks like a Swing bug, but core/windows code is also involved. Please investigate.
Comment 3 David Simonek 2007-08-16 21:45:37 UTC 
Hmm, sorry but without reproduction steps I can do nothing here, can't fix it and can't report to JDK because of random
nature of the bug. Feel free to reopen with reproducible scenario, thanks.