Server-side is not GWT's deal. "Compile in load" is only about the client.
--
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 google-web-toolkit+unsubscr...@googlegrou
I have one more question regarding this issue, I don't know if it is normal
superdevmode behavior or I am doing something wrong :
When I make a change to my war/META-INF/context.xml file and hit F5 in the
web browser, the changes are not taken into account (even if I force a
recompile by hitting
Thanks Thomas, I found some time to work on this issue and it is working
fine. To get the unpacked war directory I did unzip the war file. My
CodeServer debug launcher has 3 args: -src, -launcherDir, and the GWT
module.
--
You received this message because you are subscribed to the Google Gr
The general idea is:
* launch your app the same you'd normally do (for production), except you
don't need to compile your GWT client code, and you have to serve static assets
from a directory (i.e. not a packaged WAR but an "exploded" one, or if you're
of an "self-contained executable jar" kind
There is a way to get it working with the tomcat maven plugin with gwt
maven plugin, however I haven't had any luck with that yet. In the mean
time you can use a library I wrote up for SuperDevMode to help manipulate
compilations. Somewhat a work around to many issues but I find it helps me
out
Hi,
I would like to use superdevmode with my tomcat8 server, it doesn’t work
and I don’t see what I am doing wrong. I followed this video:
“Debugging GWT Super Dev Mode using Tomcat” (
https://www.youtube.com/watch?v=w9270Yqt-5I)
but I am getting an error HTTP 404 resource not available. When
