Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2081387 | 1.0 | Amit Handa | P2 | Resolved | Fixed | 1.0 |
Name: ygR10224 Date: 03/09/2004
Filed By : SPB JCK team (###@###.###)
JDK :
JCK : 1.5
Platform[s] : Solaris
switch/Mode :
JCK test owner : http://javaweb.eng/jct/sqe/JCK-tck/usr/owners.jto
Failing Test [s] : N/A
Specification excerpt:
======================
--------- J2SE API spec v.1.5 ---------
Javadoc for java.io.Serializable says:
...
it is strongly recommended that all serializable classes explicitly
declare serialVersionUID values, since the default serialVersionUID
computation is highly sensitive to class details that may vary depending
on compiler implementations, and can thus result in unexpected
InvalidClassExceptions during deserialization. Therefore, to guarantee
a consistent serialVersionUID value across different java compiler
implementations, a serializable class must declare an explicit
serialVersionUID value. It is also strongly advised that explicit
serialVersionUID declarations use the private modifier where possible,
since such declarations apply only to the immediately declaring
class--serialVersionUID fields are not useful as inherited members.
...
---------- end-of-excerpt ---------------
Problem description
===================
Javadoc doesn't specify the serialVersionUID for any serializable
classes in the following packages:
javax.sql.rowset
javax.sql.rowset.serial
javax.sql.rowset.spi
These may result in an unintentional serialization incompatibility
in the future. According to RFE 4525039 the serialVersionUID
should be included in the Serialized Form generated for each class.
======================================================================
- backported by
-
JDK-2081387 Javadoc doesn't specify serialVersionUID for javax.sql.rowset.* classes
- Resolved
- relates to
-
JDK-4525039 stddoclet: include serialVersionUID in Serialized Forms
- Resolved