harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zakharov, Vasily M" <vasily.m.zakha...@intel.com>
Subject RE: [classlib] serialVersionUID justification
Date Fri, 15 Jun 2007 13:21:26 GMT

As far as I know, Swing is not supposed to be serialization-compatible
not only between implementations, but even between different versions
of the same implementation.

You may see that, though Swing classes are Serializable, they do not
"Serialized form" link in the API specification, and are not listed at
"Serialized form" page.

In this situation having different serialVersionUID in Harmony than in
looks like a feature, not a bug - it makes sure that no deserialization
would be attempted in situation where compatibility is not supposed.

Also, Swing classes do not have serialVersionUID value specified in the
API specification, so we do not violate the spec by having a different
value than RI in our Swing implementation.

Note: this justification is Swing-specific and is only applicable to

Vasily Zakharov
Intel ESSD

-----Original Message-----
From: Dmitry Irlyanov [mailto:irlyanov@gmail.com] 
Sent: Friday, June 15, 2007 5:01 PM
To: dev@harmony.apache.org
Subject: [classlib] serialVersionUID justification

Harmony differs from RI implementation not only in methods
but also in class fields.
The problem is correctly stated in the JIRA issue (
https://issues.apache.org/jira/browse/HARMONY-4187 ) that says that
of serialVersionUID differ for Harmony and RI. You can see it at
http://www.kaffe.org/~stuart/japi/htmlout/h-jdk15-harmony.html , but I'm
totally confused what to do if serialVersionUID equals smth in jdk 1.5
smth else in Harmony. Should I prepare the patch that changes the values
match/be equal?
With Best Regards,
Irlyanov Dmitry

View raw message