GWT keeps track of a set of types which can be serialized and sent to the client. your.class.Type apparently was not on this list. Lists like this are stored in .gwt.rpc files. These lists are generated, so editing these lists is probably useless. How these lists are generated is a bit unclear, but you can … Read more
Ask yourself the question: “Will I need to reuse the server-side interface with a non-GWT front-end?” If the answer is “no, I’ll just have a GWT client”: You can use GWT-RPC, and take advantage of the fact that you can use your Java objects both on the server and the client-side. This can also make … Read more
did you check http://code.google.com/webtoolkit/doc/latest/tutorial/RPC.html#serialize the article says: It has a default (zero argument) constructor with any access modifier (e.g. private Foo(){} will work) I’m allways forgetting zeroargument const. when I am making a serializable object 😀
The big difference between GWT RPC and RequestFactory is that the RPC system is “RPC-by-concrete-type” while RequestFactory is “RPC-by-interface”. RPC is more convenient to get started with, because you write fewer lines of code and use the same class on both the client and the server. You might create a Person class with a bunch … Read more