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:13:16 GMT

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

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

As far as I understand it means that if someone has serialized a EmbeddedConnectionPoolDataSource40
using a 10.7 or older Derby (notwithstanding soft/hard upgrade mode at the time), and then
later try to read that serialized data source using a Derby 10.8 or newer, notwithstanding
soft/hard upgrade mode), the read would fail. The only remedy would be to use a 10.7 or older
Derby to read it, but if the user had hard upgraded already it could be a bit of a catch-22..

I presume we could put manual reading logic in place to recognize the old versioned data source
for this particular class and allow reading of the older version, and back-port such a patch,
perhaps we should file a JIRA issue for that?

I'll put together a release note for now.


                
> 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