[
https://issues.apache.org/jira/browse/DERBY-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634932#comment-13634932
]
Dag H. Wanvik commented on DERBY-6128:
--------------------------------------
Committed as svn 1469197. Commit log:
This explicit UID was missing for releases 10.10.1.1 and lower. The default
changed between 10.7 and 10.8, so even with this explicit UID in place,
serialized data sources created with 10.7 or older would not be readable. The
default UID in 10.7 was -2155993232624542236. This was not caught by the
serialization tests at the time since the "40"-suffixed data sources were not
tested back then, cf DERBY-5955
http://svn.apache.org/viewvc?view=revision&revision=1438035 .
> 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
> 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
