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 26088 - FSException on deserialization of invalid JarFileSystem on startup
Summary: FSException on deserialization of invalid JarFileSystem on startup
Status: VERIFIED DUPLICATE of bug 26072
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: rmatous
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-29 14:55 UTC by pzajac
Modified: 2008-12-22 19:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pzajac 2002-07-29 14:55:51 UTC
Netbeans ide is closed. There is moounted a
JarFileSystem in Default project Repository. Jar
file of JarFilesyetm is deleted. 

FSException is raised on start IDE:

Annotation: File
/pzajac/builds/NetBeansIDE-dev-200207100100/netbeans/lib/openide.jar
does not exist.
org.openide.filesystems.FSException: File
/pzajac/builds/NetBeansIDE-dev-200207100100/netbeans/lib/openide.jar
does not exist.
        at
org.openide.filesystems.FSException.io(FSException.java:73)
        at
org.openide.filesystems.JarFileSystem.setJarFile(JarFileSystem.java:163)
        at
org.openide.filesystems.JarFileSystem.readObject(JarFileSystem.java:543)
        at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at
java.lang.reflect.Method.invoke(Method.java:324)
        at
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:809)
        at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1733)
        at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1636)
        at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1264)
        at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:322)
        at
org.netbeans.core.projects.XMLSettingsSupport$SettingsRecognizer.readSerial(XMLSettingsSupport.java:421)
        at
org.netbeans.core.projects.XMLSettingsSupport$SettingsRecognizer.instanceCreate(XMLSettingsSupport.java:449)
        at
org.netbeans.core.projects.SerialDataConvertor$SettingsInstance.instanceCreate(SerialDataConvertor.java:315)
        at
org.openide.loaders.FolderInstance.instanceForCookie(FolderInstance.java:365)
        at
org.openide.loaders.FolderInstance$HoldInstance.instanceCreate(FolderInstance.java:783)
[catch] at
org.netbeans.core.AutomountSupport.createInstance(AutomountSupport.java:83)
        at
org.openide.loaders.FolderInstance.defaultProcessObjects(FolderInstance.java:571)
        at
org.openide.loaders.FolderInstance.access$100(FolderInstance.java:45)
        at
org.openide.loaders.FolderInstance$2.run(FolderInstance.java:456)
        at org.openide.util.Task.run(Task.java:136)

This filesystem isn't shown in Explorer. If you
open "Tools->Options" panel FSException will be
raised at first time too. You can see invalid
JarFilesystem in Options panel. The filesystem has
not property sheet. It is shown as "file.jar".
There is better to mark this filesystem as invalid
and show filesystem as "Invalid - file.jar" in
Explorer. It isn't necessary to raise exception on
deserialization of JarFileSystem if jar file
doesn't exist.
Comment 1 rmatous 2002-07-29 16:32:20 UTC
Marked as duplicate

*** This issue has been marked as a duplicate of 26072 ***
Comment 2 pzajac 2002-08-08 18:42:24 UTC
verified