If you use GWT-RPC every class that goes over the wire has to implement Serializable and must have a default constructor. Depending on your setup it can occur that the RemoteServiceServlet from GWT does not find the serialization policy file. So you should check your server logs to see if there are any serialization warnings.
Also if you are using an external server for GWT during development make sure that you first start dev mode and access your app. Then, when you got a SerializationException, redeploy your app to your external server and try it again. This ensures that your server always has the up-to-date version of the serialization policy file. When I encounter SerializationExceptions I mostly forgot to add a default constructor to my classes. So check this first! ;-) -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/q6HK4utLTgsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
