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.
[nb_release34_rc1](200207252340), [jdk1.4.0](01) Steps to reproduce: - run IDE - mount xx.jar - exit IDE - remove xx.jar - run IDE -> Exception arises with annotation "Cannot read class: org.netbeans.core.ExJarFileSystem", but annotation should be "File /home/mm119185/core25953.jar does not exist."
Created attachment 7059 [details] Wrong annotated exception
*** Issue 26777 has been marked as a duplicate of this issue. ***
I think also more to the point, this exception keeps on poping up (see issue #26777) forever and won't go away. If you must throw it, do it once and then remove the FS-dependency on behalf of the user. Or, somehow, allow him to unmount it.
I think that JarFilesystem.readObject() has incorect behaviour. It is not necesssary to throw "File xxx does not exists" exception. FileSystem has method bool isValid() ; If jar file doesn't exist it can be marked as invalid. For example if root directory in LocalFileSystem doesn't exist filesystem doesn't throw any exception on deserialization.
*** Issue 26838 has been marked as a duplicate of this issue. ***
1. Using isValid() might be difficult since (at least at one time) this was overloaded to also indicate duplicate mounts. I agree isValid() sounds right here. 2. Looks like the annotation is being attached somewhere but not displayed correctly. NbErrorManager problem, perhaps? Or problem in how annotations are propagated? 3. IMHO *all* *.settings which throw an exception while being read (InstanceCookie.instanceCreate) should be deleted from the userdir, if this is possible - not just mounts. Contrast to settings from a disabled module, which should just have no InstanceCookie at all (because the <module/> tag says not to). This bug is very frequently reported on nbusers; IMHO it should be given a high priority.
*** This issue has been marked as a duplicate of 26072 ***
Agreed.