Programmatically discovering class changes that break serialization compatibility
0 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Paul_Holser
Posted On:   Friday, June 7, 2002 03:06 PM

The serialization specification, section 5.6 names changes to a class that either break or preserve serialization compatibility--that is, you would be able or unable to read in instances of previous versions of a class in programs using newer versions of the class, depending on changes made to the class as it evolves. Has anyone given thought to a tool that can make such determinations programmatically? That is, given two class files which represent different versions of the same class, is there a tool that can read in the two class files, and ask the necessary questions of each to determine whether instances of the "older" class would be serialization-compatible with the "newer" class? I've considered building such a tool   More>>

The serialization specification, section 5.6 names changes to a class that either break or preserve serialization compatibility--that is, you would be able or unable to read in instances of previous versions of a class in programs using newer versions of the class, depending on changes made to the class as it evolves.


Has anyone given thought to a tool that can make such determinations programmatically? That is, given two class files which represent different versions of the same class, is there a tool that can read in the two class files, and ask the necessary questions of each to determine whether instances of the "older" class would be serialization-compatible with the "newer" class? I've considered building such a tool using the Jakarta BCEL, but don't want to reinvent the wheel....

   <<Less
About | Sitemap | Contact