[threeten-dev] Serialization of Chronology

[Xueming Shen]

The readResolve() in other chronology subclasses are also un-necessary
if we delegate to Ser. The Chronology.readExternal() should guarantee
the singleton via the of() lookup. But we still need to address the built-in
and user-defined override issue.

-Sherman

On 03/14/2013 12:35 PM, roger riggs wrote:
> Please review updates to address issues #283 and #279.
>
> #283: Serialization of Chronology
> #279 Inconsistent serialization for ISO chronology
>
> Cleaned up serialization for all Chronologies and added tests.
> Subclasses are enabled (as is ISOChronology) to use the Ser mechanism of Chronology.
>
> Webrev:
>    http://cr.openjdk.java.net/~rriggs/webrev-serialization-283/
>
> Thanks, Roger
>