[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new jalopy available
From: |
Michael Koch |
Subject: |
Re: new jalopy available |
Date: |
Sat, 22 Nov 2003 16:01:30 +0100 |
User-agent: |
Mutt/1.3.28i |
On Sat, Nov 22, 2003 at 07:57:55AM -0700, Eric Blake wrote:
> Michael Koch wrote:
> >
> >Serializable classes have to have their fields in the same order as in
> >in SUNs classes because of serialization issues.
>
> I thought we already had the style rule that all serialized classes provide
> an explicit serialVersionUID - because we cannot depend on the compiler to
> generate the same serial version as Sun. Case in point: when a class
> literal appears in the class, Sun emits a one-argument class$ method, but
> jikes emits a two-argument version; this affects the serial version. Also,
> as long as the serial version is correct, deserialization is name-based
> (not offset-based). Therefore, field ordering does not matter, so long as
> we provide the explicit UID.
Thx for clarifying this. It wasnt clear to me. I thought its always
offset based.
Michael
- Re: new jalopy available, (continued)
Re: new jalopy available, Mark Wielaard, 2003/11/22
Re: new jalopy available, Mark Wielaard, 2003/11/22