Have a look at https://github.com/gwtproject/gwt/tree/master/samples/mobilewebapp, we haven't had issues with AppEngine and GWT in the same Maven module (even though I discourage such usage).
On Friday, July 21, 2017 at 10:47:41 AM UTC+2, Patrick Tessier wrote: > > I'm upgrading from 2.7 to 2.8.1 now, but it seems I'm running into the > same issue as Tony. I'm using AppEngine on the server side, which is in > the same IntelliJ/Maven module as the GWT code. When launching devmode > from IntelliJ, I get "Couldn't load project from Super Dev Mode server > at...", with HTTP 500 " > > java.lang.NoSuchMethodError: > javax.servlet.http.HttpServletResponse.getHeader(Ljava/lang/String;)Ljava/lang/String;" > on the codeserver. > > I was convinced that I could rearrange the GWT/AppEngine dependencies in the > IntelliJ module and > get it working, but that appears to not be the case. So I assume that to > *run* them separately > would have to mean splitting the client and server sides into separate > pom.xml within the project > and splitting the dependencies. Correct? > > Thanks > > > On Friday, September 9, 2016 at 2:14:46 AM UTC-5, Thomas Broyer wrote: >> >> First, you don't *have* to split your project, you have to *run* them >> separately (but then you'll probably have to tweak the classpath of each a >> bit). >> >> Then, GWT RPC isn't a blocker for splitting your project (see my >> modular-webapp archetype at >> https://github.com/tbroyer/gwt-maven-archetypes) >> > -- You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
