[threeten-dev] Serialization in 310

[Stephen Colebourne]

I don't have any problem with more docs. I think we decided the enums
were best left as enums to avoid conflicts with their special
serialization.
Stephen

On 5 September 2013 14:24, roger riggs <roger.riggs at oracle.com> wrote:
> Self correction, the classes mentioned are Serializable via Enum.
>
> I'm working on an update to the documented serializable forms.
>
> Roger
>
>
> On 9/4/2013 1:30 PM, roger riggs wrote:
>>
>> Hi,
>>
>> In support of clean-room implementations, the specification of the
>> serialized
>> form for 310 needs to be more completely documented.  At present, it is
>> not
>> possible to understand the structure of a stream and the correspondence to
>> the various classes without referring to the implementation.
>> The issues are primarily documentation but a review of the serialized form
>> documentation raised some questions.
>>
>> There are several types that are not serializable that might be more
>> useful if so.
>> For example, ChronoUnit and ChronoField would be useful to be able
>> to communicate or save the state of a flexible class that could hold
>> arbitrary units or fields.
>>
>> There are some inconsistencies too, WeekFields is Serializable but
>> ISOFields and JulianFields are not.
>>
>> Roger
>>
>> p.s.
>>
>> There is an issue based on the conformance issues:
>>
>>  * JDK-8024164 <http://bugs.sun.com/view_bug.do?bug_id=8024164> JSR310
>>    serialization should be described in details
>>
>