Note that there are some explanatory texts on larger screens.

plurals
  1. POGWT/appEngine RPC serialization
    text
    copied!<p>Up until last week I have been running my GWT/AppEngine app with no problems using java.io.Serializable and implements Serializable on my classes in RPC calls.</p> <p>Now I get this error on appengine: Type 'com.foobar.web.shared.RPCDTOclass' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer.</p> <p>I still have the implements Serializable. If I fix/change that class and make it com.google.gwt.user.client.rpc.IsSerializable it works for that class but I get the same error for other classes used in RPC. I only have Strings in some of them, so it isn't that I have types that I can't serialize.</p> <p>I don't see anyone else having this problem so I must have made some type of change that is causing it, but I don't know what. The error shows up on AppEngine, so I think it must be an appengine problem?</p> <p>Thanks</p> <p>Adding an example</p> <pre><code>public class UserLogInDTO implements IsSerializable { private String Email; private String PasswordHash; public UserLogInDTO(){} public UserLogInDTO(String email, String passwordhash){ setEmail(email); setPasswordHash(passwordhash); } public void Set(String email, String passwordhash){ this.setEmail(email); this.setPasswordHash(passwordhash); } /** * @return the email */ public String getEmail() { return Email; } /** * @param email the email to set */ public void setEmail(String email) { Email = email.toLowerCase(); } /** * @return the passwordHash */ public String getPasswordHash() { return PasswordHash; } /** * @param passwordHash the passwordHash to set */ public void setPasswordHash(String passwordHash) { PasswordHash = passwordHash; } </code></pre> <p>}</p> <p>If I have implements IsSerializable it works, if implements Serializable it used to work but now doesn't. I am using 1.7.2 SDK for AppEngine 2.4.0 for GWT</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload