[
https://issues.apache.org/jira/browse/DERBY-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613505#comment-13613505
]
Dag H. Wanvik commented on DERBY-6128:
--------------------------------------
EmbeddedConnectionPoolDataSource40 should be serializable across VMs, cf. our
tests in DataSourceSerializationTest, so I still
believe we need to add it there. The persistent data sources are produced by
org.apache.derbyTesting.functionTests.testData.serializedDataSources.SerializeDataSources,
a standalone program.
> 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
> Reporter: Rick Hillegas
> Attachments: 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
