That would be a very silly idea, and not necessary. If you deploy an exploded WAR (with application class files and resources on the file system, not inside a WAR file) you can get hot swapping (but you'll need to run in development mode in 5.3, which turns off live class reloading in production).
On Mon, Oct 10, 2011 at 12:17 PM, Dmitry Gusev <dmitry.gu...@gmail.com> wrote: > Eclipse is not a web container, so you're not running Tapestry in Eclipse > anyway. > > On Mon, Oct 10, 2011 at 22:42, Bryan Lewis <jbryanle...@gmail.com> wrote: > >> This might be a silly idea, but I'll ask it anyway... Would it be bad to >> run a Tapestry application inside Eclipse on a production server? The >> objective would be to have full hot-swapping, as I have in my local >> development workspace, but maybe it would be bad for memory consumption or >> stability. >> > > > > -- > Dmitry Gusev > > AnjLab Team > http://anjlab.com > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
