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

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.11.1.1
• Component/s: JDBC
• Issue & fix info: Release Note Needed
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 22/Mar/13 18:54
• Updated: 09/Jun/14 13:30
• Resolved: 18/Apr/13 07:21

Description

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.

Issue Links

• relates to: DERBY-6124 Marshalling error in JDBCDriverTest as part of CompatibilityTest
• relates to: DERBY-6204 Add logic to read 10.7 and earlier versions of EmbeddedConnectionPoolDataSource40
• relates to: DERBY-6314 Upgrade from 10.10 fails with ClassCastException