db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6128) Examine Derby classes to determine if we need to add serialVersionUID to any of them
Date Fri, 19 Apr 2013 04:23:20 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636053#comment-13636053
] 

Dag H. Wanvik commented on DERBY-6128:
--------------------------------------

Note that the patch committed doesn't introduce any regression, it merely fixes the version
number going forward.  The regression happened in 10.8, since by then there was no explicit
serialVersionUID, so Java computes one based on the class dependencies. Obviously, that must
have changed between 10.7 and 10.8 for the (implicit) version number to change the way it
did.

But since our content of the serialized class didn't really change it would be good to install
logic to recognize and accept both the pre-10.8 and post-10.7 version numbers when reading
a serialized class instance.

                
> Examine Derby classes to determine if we need to add serialVersionUID to any of them
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-6128
>                 URL: https://issues.apache.org/jira/browse/DERBY-6128
>             Project: Derby
>          Issue Type: Task
>          Components: JDBC
>            Reporter: Rick Hillegas
>             Fix For: 10.11.0.0
>
>         Attachments: derby-6128-ecpds40.diff, SerializableLister.java
>
>
> The discussion on DERBY-6124 has raised the possibility that we may need to add serialVersionUIDs
to some serializable Derby classes. Without the serialVersionUIDs, Derby may encounter deserialization
errors on objects which were serialized by one version of Derby or the JVM and then deserialized
by another version of Derby or the JVM.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message