[concurrency-interest] Concurrent Serialization Pattern

David Holmes dcholmes at optusnet.com.au
Thu Sep 14 21:19:51 EDT 2006


> I didn't realize that the final sematics had
> precedence over the transient qualifier, so I incorrectly thought that
> lock would have the default null value after deserialization.

According to my reading of the serialization spec it *should* have a null
value. transient fields don't get serialized, unless you custom serialize
them. So a transient final field should have its default initialized value
when readObject is invoked.

Something seems amiss here.

David Holmes

More information about the Concurrency-interest mailing list