Friday, January 31, 2014

GWT 2.6.0, SuperDevMode, and GWT-RPC serialization error

I have switched over a new project to GWT 2.6.0. I running with Maven and the GWT Maven Plugin 2.6.0-rc3.

Everything was working swimmingly with GWT 2.5.1. Now I'm getting GWT-RPC serialization errors when running SuperDevMode.

If I start DevMode from Maven (gwt:run) or through Eclipse, the classes that I have marked as implementing pass through the RPC layer without a hitch. However, serialization fails with SuperDevMode:
- start SuperDevMode from a console with Maven and gwt:run-codeserver)
- start the server though Eclipse in Development Mode
- on the Development Mode messsage, 
  open the URL
- turn Dev Mode On and Compile

Now executing the GWT-RPC method shows this in my console file:

Starting Jetty on port 8888
   [WARN] Exception while dispatching incoming RPC call Type '' was not assignable to '' and did not have a custom field serializer.For security purposes, this type will not be serialized.: instance =
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at org.eclipse.jetty.servlet.ServletHolder.handle(
at org.eclipse.jetty.servlet.ServletHandler.doHandle(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.session.SessionHandler.doHandle(
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
at org.eclipse.jetty.servlet.ServletHandler.doScope(
at org.eclipse.jetty.server.session.SessionHandler.doScope(
at org.eclipse.jetty.server.handler.ContextHandler.doScope(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at org.eclipse.jetty.server.handler.RequestLogHandler.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at org.eclipse.jetty.server.Server.handle(
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(
at org.eclipse.jetty.server.AbstractHttpConnection.content(
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(
at org.eclipse.jetty.http.HttpParser.parseNext(
at org.eclipse.jetty.http.HttpParser.parseAvailable(
at org.eclipse.jetty.server.AsyncHttpConnection.handle(
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
at org.eclipse.jetty.util.thread.QueuedThreadPool$
[ERROR] 500 - POST /optixm/mobile ( 57 bytes
   Request headers
      Connection: keep-alive
      Content-Length: 137
      X-GWT-Permutation: FAC089581D0988AAD23493D0B52C84AF
      User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.102 Safari/537.36
      Content-Type: text/x-gwt-rpc; charset=UTF-8
      Accept: */*
      DNT: 1
      Accept-Encoding: gzip,deflate,sdch
      Accept-Language: en-US,en;q=0.8
      Cookie: JSESSIONID=11w6l0ygma6brge4d71mphf48
   Response headers
      Content-Type: text/plain

If I implement AboutBoxData with vs, the class will eventually fail because of a member that uses

What could be causing this? I've cleaned my Maven tree down to pom.xml and src, but each time I get this error. 

Is there some new setting to gwt-maven-plugin?

Is there some Eclipse plugin I should|should not be running? My Eclipse has installed m2e from and m2e-apt and m2e-wtp from   I have removed the Jetty plugins I was using elsewhere.

Thanks for y'all's help. I want to run 2.6.0 because I want to work with the latest MGWT SNAPSHOTS as they are available, and I don't want to give up SuperDevMode.

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment