On Thursday, March 14, 2013 1:31:50 AM UTC+1, kabram wrote: > > Our setup is as follows: > - Server code runs in a tomcat instance. Our ant build process > compiles and sets up the server war. As part of the build, GWT is also > built. > - We compile the client side code in dev-mode or super-dev mode. > > Symptom: > - As soon as we make changes to the client code, we get intermittent > RPC serialization errors. What we see is that the RPC comes with a > strong-name that is not available in the server side (i.e., > <strong-name>.gwt.rpc file isn't there). When this happens, GWT uses > LegacySerializationPolicy which only accepts IsSerializable. All our code > now extends this but we also have third-party code that only implements > java.io.Serializable. > > Work-around; In dev-mode, we've set the output to compile into Tomcat's > web app directory so that new RPC manifests are found. But super-dev mode > creates new directories and cannot be made to output to a deterministic > folder. I can't believe we are the first to encounter this? >
You're not: https://code.google.com/p/google-web-toolkit/issues/detail?id=7522 > > What are our options? Not use super-dev? Override the > RemoteServiceServlet's method that retrieves the RPC file and look through > super-dev's output folders? > The latter is what people have done (IIRC the threads in this group), and this is what will be done in GWT (see the latest update to the above-mentioned issue) -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
