Ok, solved... Just needed to upgrade my gwt-servlet.jar (the most obvious error :-)).
Thanks anyway. Lorenzo On Feb 16, 3:47 pm, "l.denardo" <[email protected]> wrote: > Hello, > I'm currently facing an issue while upgrading to gwt 2.2. > > My application uses spring on server side, and gwt dispatch for > communication. > Strack trace is > SEVERE: Exception while dispatching incoming RPC call > java.lang.NullPointerException > at javax.servlet.GenericServlet.getServletName(GenericServlet.java: > 238) > at javax.servlet.GenericServlet.log(GenericServlet.java:204) > at > com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java: > 211) > at > com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java: > 243) > at > com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java: > 62) > at > it.miriade.planner.server.service.BaseRemoteService.handleRequest(BaseRemoteService.java: > 25) > > etc. > > This issue (I faced it in the past) is due to new compilation of GWT > modules, and subsequent variation in serialization policy files, which > make the old rpc service incompatible with the new compiled module. > > I noticed that GWT 2.2 compiles some files under WEB-INF/deploy/ > which look related to serialization policy, and so to this bug. What I > need to know is how this output folder can be configured, and if > there's a workaround to make the policy files easily accessible > (taking them out of WEB-INF if this is not an issue). Or maybe if this > incompatibility is due to other issues. > > Thanks to everyone > Lorenzo -- 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.
