Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 18 Apr 2013 07:21:24 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12638566.1363978444479.184957.1366269684102@arcas>
In-Reply-To: <JIRA.12638566.1363978444479@arcas>
References: <JIRA.12638566.1363978444479@arcas>
Subject: [jira] [Resolved] (DERBY-6128) Examine Derby classes to determine
 if we need to add serialVersionUID to any of them
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik resolved DERBY-6128.
----------------------------------

          Resolution: Fixed
       Fix Version/s: 10.11.0.0
    Issue & fix info:   (was: Patch Available)
    
> 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
>             Fix For: 10.11.0.0
>
>         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