Page History

...

As a result, developers need neither maintain the earlier version of the code nor explicitly support the original serialized form.

Wiki MarkupNote that compliance with this rule, while necessary, is not sufficient to guarantee compatible evolution of serializable classes. For a full discussion of comptabile evolution of serializable classes, see the Java Object Serialization Specification (version 6), Chapter 5: Versioning of Serializable Objects \[ [Sun 2006|AA. References#Sun 06]\].

Noncompliant Code Example

...

Bibliography

...

[ [API 2006AA. References#API 06]]		]]></ac:plain-text-body></ac:structured-macro>	<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1e1e1904-07da-481f-bef2-6667ebeab0a4"><ac:plain-text-body><![CDATA[
[ [Bloch 2008AA. References#Bloch 08]]	Item 74, Implement serialization judiciously	]]></ac:plain-text-body></ac:structured-macro>	<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="736e1e61-aaa1-4c32-ad8a-294133b02cf4"><ac:plain-text-body><![CDATA[
[[Harold 2006AA. References#Harold 06] ]	13.7.5, serialPersistentFields	]]></ac:plain-text-body></ac:structured-macro>	<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4338850d-2515-4786-8233-05e92440d0c8"><ac:plain-text-body><![CDATA[
[[Sun 2006AA. References#Sun 06] ]	Java Object Serialization Specification ]]></ac:plain-text-body></ac:structured-macro>

...

13. Serialization (SER)      13. Serialization (SER)