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 64018 - InvalidObjectException when using apisupport wizard to insert class reference not already in classpath
Summary: InvalidObjectException when using apisupport wizard to insert class reference...
Status: RESOLVED DUPLICATE of bug 66252
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-10 00:03 UTC by Rich Unger
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stack trace (2.64 KB, text/plain)
2005-09-10 00:04 UTC, Rich Unger 		Details
full log file (329.17 KB, text/plain)
2005-09-12 18:41 UTC, Rich Unger 		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 Rich Unger 2005-09-10 00:03:11 UTC 
Using Nightly Build 200509051800

I used the apisupport Action wizard to create a new CookieAction whose
cookieClasses() contains DataObject.class.  DataObject was not in the imports
section, however, and the module was not already dependent on the DataSystems
API module.  So, when I manually (through the project's properties UI) added
this dependency, and then tried to fix imports (to get DataObject in the
imports), I got an InvalidObjectException.

I continued getting the stack trace whenever I tried to do autocompletion or fix
imports until restarting netbeans.

stack trace attached.
Comment 1 Rich Unger 2005-09-10 00:04:00 UTC 
Created attachment 24671 [details]
stack trace
Comment 2 Martin Matula 2005-09-10 08:09:09 UTC 
Could you please attach the whole messages.log? Thanks.
Comment 3 Rich Unger 2005-09-12 18:41:59 UTC 
Created attachment 24712 [details]
full log file
Comment 4 Rich Unger 2005-09-12 18:42:25 UTC 
No problem.  messages.log is now attached.
Comment 5 Matthew Stevens 2005-09-17 03:12:49 UTC 
I have the same stack trace in dual proc Win2000 Sep8 Qbuild.  My only criteria
to add is

I have the same QBuild installed on single proc XP with same version of Java
5-04 and I have the same scenario for IDE usage.  I have the NB src unzipped and
I have opened a few dozen projects and I am looking at code, using the
Navigator.  On my  single processor I have not had any stack trace for a week 
but I get stack trace many times a day on dual proc.  After I record any other
stack traces - I have others and one which persists where I need to kill IDE and
in one case the memory ran off to full mx and I killed IDE too.  I am open to
the idea that my userdir is screwd and so I will make a new userdir and remount
the projects and see if problem persists.
Comment 6 Jan Becicka 2005-10-25 15:40:52 UTC 

*** This issue has been marked as a duplicate of 66252 ***
Comment 7 Quality Engineering 2007-09-20 12:07:13 UTC 
Reorganization of java component