Monday, May 26, 2014

Re: Google Chrome 35 GWT plugin incompatibility



On Saturday, May 24, 2014 1:08:47 PM UTC+2, Vassilis Virvilis wrote:
Aha,

I am not into maven (yet) but the equivalent in ant land I suppose is __reload__ task http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Reload_An_Existing_Application

This coupled with some ant rsync magic can  drop my redeployment down to 4sec. No web.xml reloads though...

I think all you actually need is a context.xml file in Tomcat's $CATALINA_BASE/conf with a docBase pointing to your "war" folder, reloadable="true" to automatically reload your app whenever a class or resource changes, and possibly a Loader to load classes from outside WEB-INF/classes and WEB-INF/lib (use a VirtualWebappLoader then).
Then you don't need to copy anything to Tomcat to deploy your app (just start it), or redeploy it (just save your *.java file, let your IDE recompile it and then Tomcat pick it up and reload the webapp automatically for you).

See http://tomcat.apache.org/tomcat-7.0-doc/config/context.html and http://tomcat.apache.org/tomcat-7.0-doc/config/loader.html

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment