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 44846 - NPE from JarFileSystem.refreshExistingFileObjects
Summary: NPE from JarFileSystem.refreshExistingFileObjects
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: rmatous
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-06-14 23:48 UTC by Jesse Glick
Modified: 2008-12-22 19:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jesse Glick 2004-06-14 23:48:00 UTC 
040614. While doing a real-clean or similar.

Note that you still have the hack in to skip null
FileObject entries from existingFileObjects:

Enumeration en = existingFileObjects (getRoot ());
while (en.hasMoreElements()) {
    AbstractFolder fo =
(AbstractFolder)en.nextElement();
    if (fo == null || (fo.isFolder() &&
!fo.isInitialized())) continue;
    String[] children =
cache.getChildrenOf(fo.getPath()); // HERE

so I guess this means that cache is not, null fo.

Which isn't very surprising, since getCache does
not guarantee a non-null return value. parse can
return null for various reasons (including
silently swallowing Throwable - very very bad!).
Comment 1 rmatous 2004-06-16 15:35:19 UTC 
/cvs/openide/src/org/openide/filesystems/JarFileSystem.java
new revision: 1.94; previous revision: 1.93
Comment 2 Marian Mirilovic 2005-12-20 15:49:18 UTC 
This issue was solved long time ago. Because nobody has reopened it neither
added comments, we are verifying/closing it now. 
If you are still able to reproduce the problem, please reopen. Thanks in advance.