Aaron M. Renn wrote:
>
> So I'm trying to make my security classes compatible with the JDK from a
> serialization standpoint and I think there are still problems even with the
> new docs. The serialized form of the public classes are defined, but not
> the internal classes.
>
> [example snipped]
>
> Any thoughts on this? Am I missing something or is this a real problem?
Yes! I submitted this exact bug report to JavaSoft just yesterday as I
realised it was true for many non-public or inner classes within
Collections. I'll provide a bug number as soon as I get one, and I'll
put at least 1 of my bug votes onto it too.
I'm very pleased to hear that it is also a problem for other parts of
the spec, actually, because if it were only collections it would
probably be prioritised fairly low.
For a spec that is supposed to be stable and implementable, beta4 has a
long way to go - I found another significant spec bug in the latest
changes to java.util.List also, which will make some common methods in
spec-conforming classes O(n) when a better designed spec could make them
O(1).
Okay, rant over. I just sincerely hope that Sun fix these, and quickly.
Stuart.
