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 16151 - DESERIALIZATION problem: IOE, ISE, IError are thrown after import project from FFJ20
Summary: DESERIALIZATION problem: IOE, ISE, IError are thrown after import project fro...
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: mslama
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-03 08:13 UTC by dmladek
Modified: 2008-12-23 09:34 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stackTraces of deserialization problem (11.61 KB, text/plain)
2001-10-03 08:17 UTC, dmladek 		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 dmladek 2001-10-03 08:13:45 UTC 
[NBdev-200110030100]
jdk1.3.1, rh71
====================

I took clear build without userdir settings, so the Import Wizard appeared.
This Wizard allowed me import only Project from FFJ20 (the dialog was saying
entr install dir of Previous  version).
So, I've imported it and after Import finished....IDE started up.
a few problems arrays. Here I mentioned Deserialization problem in openide/loaders

pls, see attached E.
this has to be marked as P1-Beta Stoper
Comment 1 dmladek 2001-10-03 08:17:18 UTC 
Created attachment 2815 [details]
stackTraces of deserialization problem
Comment 2 _ ttran 2001-10-03 08:27:14 UTC 
Exceptions thrown from window system but getNodeDeleagate is also
called from invalid DataObjects, thus cc vstejskal
Comment 3 Vitezslav Stejskal 2001-10-03 09:06:07 UTC 
I think it is similar problem like issue #15615. I didn't trace the 
code, but generaly you shouldn't call getNodeDelegate for an invalid 
DataObject. In this particular case it seems that EditorSuport 
serializes DataObject and this DO isn't valid after the 
deserialization. I am not sure why, it could also be a problem in Data 
Systems, I will look at it closer.

(CCing Jesse - he helps with DataSystems and Svata because it's in 
fact problem with JavaEditor)
Comment 4 Jan Zajicek 2001-10-03 12:04:44 UTC 
Noticed the same problem - I had in old ffj20 project opened one file
in the editor - after import got the same exception caused by calling
getNodeDelegate on invalid DataObject - the editor wasn't opened.
Comment 5 mslama 2001-10-03 13:02:49 UTC 
Added check to avoid call of getNodeDelegate() on invalid data object
in method readExternal() of org.openide.text.EditorSupport$Editor.

This deserialized top component is discarded later anyway in
readResolve() when its data object is invalid. (Happens for example
when its content (file object) does not exists eg. after import so
it is useless to open empty editor. It means that behaviour that
editor is not opened is correct in given case. Fix just avoids raising 
exception caused by performing invalid call in given context.)

Fixed in main trunk.
Comment 6 Marian Mirilovic 2002-10-25 14:27:10 UTC 
verified
Comment 7 Quality Engineering 2003-07-01 16:47:58 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.