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 6976 - Problem with deserialization during startup
Summary: Problem with deserialization during startup
Status: CLOSED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P1 major (vote)
Assignee: Svata Dedic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-07-04 13:07 UTC by Jan Chalupa
Modified: 2007-09-26 09:14 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Log file (9.65 KB, text/plain)
2001-07-20 20:46 UTC, Jan Chalupa 		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 Jan Chalupa 2000-07-04 13:07:39 UTC 
Upon startup, "... could not deserialize ..." message box was displayed and
java.lang.ClassCastException and java.io.IOException were thrown.

Log file attached.
Comment 1 Jan Chalupa 2000-07-04 13:09:59 UTC 
Created attachment 19 [details]
Log file
Comment 2 Jaroslav Tulach 2000-07-04 14:05:59 UTC 
Might be caused by an object having field pointing directly to Element.Impl and
serializing it. Serialization is ok, but the deserialization replaces the
Element.Impl by its Element (readResolve method), that is the reason why it
throws the ClassCastException.
Comment 3 Jesse Glick 2000-08-23 15:25:59 UTC 
Is this still true? Two things look old about this bug: one, the global property
sheet should no longer be attempting to serialize nodes; only local property
sheets should be doing this now, and it is probably not common for someone to
open and leave open a property sheet for an element node. Two, I thought I saw
some change by Svata correcting serialization problems in elements; did this
solve all of them?
Comment 4 Svata Dedic 2000-08-23 15:57:59 UTC 
I really can't reproduce the bug in recent builds. But neither I can find a
bugfix that would fix the described bug for sure.
Comment 5 Quality Engineering 2003-07-01 13:12:50 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 6 Quality Engineering 2003-07-01 13:20:59 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.