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 56698 - InvalidObjectException: Object with MOFID [guid] no longer exists
Summary: InvalidObjectException: Object with MOFID [guid] no longer exists
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Pokorsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-20 21:56 UTC by _ pcw
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack trace (1.37 KB, text/plain)
2005-03-20 21:57 UTC, _ pcw
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ pcw 2005-03-20 21:56:35 UTC
I get "javax.jmi.reflect.InvalidObjectException: Object with MOFID
2B16BEC0-996E-11D9-87CA-4E8DEC55AA77:0000000000000DEC no lon
ger exists." quite a bit from MDR while using NB 4.1 and creating web service
clients.

It seems to be related the MDR's processing of the webservice client files
themselves.

You can view the files in the IDE by creating a web application, add a web
service client, build the project, then go to the files tab and open the
directory [webapp]/build/generated/wssrc/[package of generated client]/

When you do open the client directory, you'll briefly get the scanning dialog
the first time [momentary segue: I think this might be a bug, in that I believe
the files should have been scanned when they were generated.  Users would not
normally browse to this directory, but the interfaces here do need to be in MDR
for code completion to work propertly]

Now go back to the project tab and execute "Clean & Build" project.  This will
delete the client files and then wscompile will regenerate them.  Then go back
to the files tab and look at the client again.  It is after I've done this once
or twice, or maybe some other things in the IDE, that I get these exceptions. 
I'm not 100% certain, but this appears to be the common behavior and I get these
exceptions alot when I'm continually rebuilding and inspecting the client files,
but not at other times.
Comment 1 _ pcw 2005-03-20 21:57:24 UTC
Created attachment 20968 [details]
stack trace
Comment 2 Martin Matula 2005-03-21 09:54:09 UTC
Seems like a bug in JavaNode - it obtains a resource and then tries to access it
in a transaction. But the code for getting to the resource is in a separate
transaction than the code for extracting the data from it. Reassigning to java.
Honzo, please look at it.
Comment 3 Jan Pokorsky 2005-03-24 14:25:36 UTC
fixed in

/cvs/java/src/org/netbeans/modules/java/JavaNode.java
new revision: 1.127; previous revision: 1.126