On Wednesday, June 13, 2012 7:53:35 PM UTC+2, Andrea Boscolo wrote: > > I can confirm that copying the CodeServer's .gwt.rpc files in the local > war dir, works but it's a pain: every time they change, they need to be > copied. > Using a -workDir under the war didn't work for me. The CodeServer output > directory structure does not help. >
That was: in addition to the following (loadSerializationPolicy), and for AppEngine (because you cannot use java.io.File to look outside your WAR –I'm not even sure you can use it to look *inside* it, but maybe you could use ServletContext#getResourcePaths to find the latest compilation from SuperDevMode and then use getResourceAsStream to load the gwt.rpc file from there–) > In http://tbroyer.posterous.com/how-does-gwts-super-dev-mode-work (thanks > for the clarifications Thomas) is it said that can be possible to override > loadSerializationPolicy to search for the SuperDevMode app space. Haven't > tried yet, I'll find the time to check this out. > Anyway, seems strange that the new development mode does not work well > with GWT-RPC. Probably I see the problem from the wrong point of view. As I wrote on my blog, SuperDevMode (currently) only handles client-side code, and GWT-RPC needs both sides to be in perfect sync. -- 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/-/px1QQyy9_n4J. 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.
