|
Quick Lists
|
|
Bug ID:
|
4379111
|
|
Votes
|
0
|
|
Synopsis
|
Adding a new field breaks serialization compatibility
|
|
Category
|
idl:serialization
|
|
Reported Against
|
ladybird
|
|
Release Fixed
|
|
|
State
|
11-Closed, duplicate of 4365188,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
4365188
|
|
Submit Date
|
13-OCT-2000
|
|
Description
|
As per the serialization spec on http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/version.doc8.html, adding a new field to a class is a compatible change for serialization. This means that if a class is evolved by adding a new field, then the new class and the original class can be serialized and deserialized amongst them with out any version mismatch. However it does not seem to happen so.
I've demonstrated the problem to Everett. A detailed report for serialization test execution against rip-int could be found at javaweb.eng/~arung/corba/merlin/serialization/evolution/ser.result.txt.
Thanks,
Arun
|
|
Work Around
|
N/A
|
|
Evaluation
|
N/A
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |