[ https://issues.apache.org/jira/browse/DERBY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568010#action_12568010 ]
Kristian Waagan commented on DERBY-1318: ---------------------------------------- I will commit the patch under this issue tomorrow if nobody objects. > Add an upgrade test to verify that DataSources can be serialized by the > previous release and then correctly deserialized by the current release > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1318 > URL: https://issues.apache.org/jira/browse/DERBY-1318 > Project: Derby > Issue Type: Test > Components: JDBC, Test > Affects Versions: 10.2.1.6 > Reporter: Rick Hillegas > Attachments: derby-1318-1a-for_comments.diff, > derby-1318-1a-for_comments.stat > > > Currently, our DataSources are serializable in order to play well with JNDI. > However, we have no upgrade test verifying that DataSource serialization > works across release boundaries. We should add this case to our upgrade tests. > Further recommendations by Dan: > "I do think though that upgrade testing recently brought into the mainline by > Deepa should be enhanced to test: > - serializing Derby''s data source implementations in 10.1 and seeing it > unserializes with 10.2 > (maybe into a BLOB column) > - making a Reference object out of Derby''s data source implementations in > 10.1 and making it into > an object with 10.2. (if this type of tetsing makes sense for > References')" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.