[
https://issues.apache.org/jira/browse/DERBY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas closed DERBY-1318.
--------------------------------
Resolution: Fixed
> 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: Improvement
> Components: JDBC, Test
> Affects Versions: 10.2.1.6
> Reporter: Rick Hillegas
> Labels: derby_triage10_8
> Attachments: derby-1318-1a-for_comments.diff,
> derby-1318-1a-for_comments.stat, derby-1318-1b-for_comments.diff,
> derby-1318-1b-for_comments.stat, derby-1318-2a-javadoc_and_build.diff,
> serialized-data-sources.zip
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
