You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/06/14 19:08:21 UTC

[jira] [Closed] (DERBY-6128) Examine Derby classes to determine if we need to add serialVersionUID to any of them

     [ https://issues.apache.org/jira/browse/DERBY-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas closed DERBY-6128.
--------------------------------

    
> 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, releaseNote.html, 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