On Thu, Sep 24, 2009 at 6:49 AM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > Em Thu, 24 Sep 2009 10:46:31 -0300, Ilya Obshadko <ilya.obsha...@gmail.com> > escreveu: >> Live class reloading is a great feature. >> But I couldn't figure out yet how one should configure, for example, >> Tomcat 6 in development environment to avoid redeployments after each and >> every >> change in the code. Are there any solutions? > Use Jetty instead: faster, simpler, more modular. :) Take a look at the > reloadable attribute in the Context tag. Try making your context not > reloadable.
That's simply not true. I love Jetty and it's very well implemented but the core Tomcat runs and starts up just as fast as Jetty. I bet Ilya's issue is he tries to use Eclipse own JEE container support, which is using the traditional concept - copy files, redeploy application on change. Use run-jetty-run or sysdeo's Tomcat plugin with Eclipse (or http://merve.sourceforge.net/ for Tomcat similar run-jetty-run but the development stalled). I prefer sysdeo's because it has much finer control of the application classpath. Note that while I use Tomcat for development my designers happily run mvn jetty:run and edit the live templates without ever really having to understand and worry about the underlying machinery. Kalle --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
