Thanks a bunch. It's working now. I did try that at some point, but it
didn't work. I just though that if the deserialization mechanism uses
the no args constructor, and my final field is instantiated inside the
no args constructor, all is fine. I now understand that after the
first initialization inside of the no args constructor, the
deserialization tries to change the reference of the final field and
cannot. But why in the name of ... doesn't it just throw some kind of
fit or exception when it cannot reinitialize the final field? Anyways,
thanks.
On Sep 10, 4:35 pm, Paul Robinson <[EMAIL PROTECTED]> wrote:
> Final fields are not serialized. Just remove the word "final".
>
> Eugen Paraschiv wrote:
> > public class A<T extends B> implements IsSerializable {
> > private final List<T> items;
>
> > What currently happens is this: I send a object of type A and the
> > object is sent OK, but on the other side, the 'items' collection is
> > empty.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
