[ http://jira.jboss.com/jira/browse/JBAS-1579?page=history ]
Clebert Suconic reassigned JBAS-1579: ------------------------------------- Assign To: Scott M Stark (was: Clebert Suconic) I've created a TestCase that: - tests if all classes in a given JAR have the SerialUID - tests if all classes in all equivalent JARs at the same version have the SerialUID - If the default constructor is available, serialize the class and verify if it can be deserialized in the new version. I've ran the testcase against jboss-all.jar Questions: Do you think this testcase is enough for the test-compatibility? I'm going to add this into jboss-head, and test the backward compatibility through jboss-4 and jboss-3 what will cover all versions. I didn't add the test into CVS yet (at the time of this comment). Please, after you have read and evaluated this comment, assign me the activity back. > Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes > ----------------------------------------------------------------------------- > > Key: JBAS-1579 > URL: http://jira.jboss.com/jira/browse/JBAS-1579 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Reporter: Scott M Stark > Assignee: Scott M Stark > Priority: Blocker > Fix For: JBossAS-4.0.2 Final > Attachments: SerializableHasSerialVersionUIDField.zip, TestResultSample.zip > > > I'm seeing incomptibilities between versions that are simply due to the fact > that Serializable/Externalizable classes are letting their serialVersionUIDs > float instead of explicitly defining them. We need to get this cleaned up. > There should not be a single Serializable/Externalizable class that does not > fix its serialVersionUID and then take responsibility for maintaining > compatibility with the indicated version. > The attached SerializableHasSerialVersionUIDField.zip unzips to create a > SerializableHasSerialVersionUIDField-index.html and > SerializableHasSerialVersionUIDField directory which is a report of all > classes in the 4.0 codebase that are not defining a serialVersionUID as they > should. > The JDK object serialization spec defines all you need to know about the apis > and contracts for object serialization: > http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/serialTOC.html > In particular, Versioning of Serializable Objects: > http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/version.html#wp9419 > talks about binary compatibility and what is available to manage this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development