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 53869 - IOE: Mofid no longer exist
Summary: IOE: Mofid no longer exist
Status: CLOSED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Daniel Prusa
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-01-24 10:06 UTC by Milan Kubec
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
exc stack trace (8.30 KB, text/plain)
2005-01-24 10:07 UTC, Milan Kubec
Details
Similar stack trace, when doing a "fix import command" (24.79 KB, text/plain)
2005-04-05 08:58 UTC, cberger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kubec 2005-01-24 10:06:45 UTC
[dev-200501231900, JDK 1.5.0_02]

I created simple class and used class File in it.
java.io.File wasn't in the import so I used
Alt+Shift+I to add it and InvalidObjectException
was thrown and NullPointerException after that
when clicking back to code editor (at least I
think). Both exceptions are attached.
Comment 1 Milan Kubec 2005-01-24 10:07:10 UTC
Created attachment 19894 [details]
exc stack trace
Comment 2 Martin Matula 2005-02-11 15:44:37 UTC
Unfortunatelly, I can see nothing from the stacktraces. In the future,
the whole messages.log would be more useful since the error may be a
consequence of some inconsistency that was there before.
I am also not able to reproduce this issue. For now I will set this as
incomplete. Please provide new stacktrace if it happens again. Thanks
and sorry.
Comment 3 cberger 2005-04-05 08:58:56 UTC
Created attachment 21371 [details]
Similar stack trace, when doing a "fix import command"
Comment 4 Martin Matula 2005-04-05 09:08:13 UTC
Seems like a different issue. Dan please look at it.
Comment 5 Daniel Prusa 2005-09-15 09:46:03 UTC
InvalidObjectException in the second attachment is duplicate of issue 57067.
Comment 6 Daniel Prusa 2005-09-27 14:52:37 UTC
I am not able to reproduce any of the two reported problems. As I have already
noted the second stack trace duplicates issue 57067 which is related to
InvalidObectException during Fast Import and Fix All Imports actions. I will
close this issue as non-reproducible. Progress on InvalidObjectExceptions during
fast import can be still tracked in 57067.
If the excpetion is still reproducible in the latest dev builds it would be
helpfull if you could describe steps leading to this situation and attach
related sources.
Comment 7 Milan Kubec 2005-12-19 15:54:43 UTC
Verified.
Comment 8 Quality Engineering 2007-09-20 12:49:33 UTC
Reorganization of java component