I'm using GWT 2.0.3 and have encountered a problem during async rpc.
I have a serializable class containing a number of other serializable
class. E.g.
class Parent implements java.io.Serializable {
private ChildA childA;
private ChildB childB;
private ChildC childC;
private ChildD childD;
......
}
each of the Child classes are also serializable and can be passed over
async rpc without any problem. However, when I pass this class over
async rpc, no matter it's from server to client or vice versa. Some
of the child instances will get lost and become null. It's very
annoying as whenever a new variable is added to that Parent class, a
different combination of child instances will get lost.
I'm using that parent class to maintain the state of the application
when closing and opening the app. Of coz I can pass each child
instance individually in a single rpc when saving the states to the
server. But when retrieving the states back from the server, it will
be extremely messy to call 10 different async rpc and check if all
child instances are ready on each and every onSuccess method.
I didn't receive any warning or exception during compile or run time.
I'm not sure if it's a bug of GWT or it's simply not supported. Can
anyone suggest what should I do to fix it or get around with it?
Thanks.
Yau
--
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.
