Re: running eclipse in production
On Tue, 11 Oct 2011 13:12:08 -0300, Bryan Lewis wrote: But the lower-level classes, not part of Tapestry's domain, don't reload. For example, I've got business logic in my domain objects, in a lower-level "model.jar". I've tried running with that jar exploded and updating the .class files but the changes don't get picked up. The eclipse maven plugin handles that for me in my development workspace, which is what sparked the question. What web container do you use? They usually have some configuration to auto-redeploy applications when some class is changed, and I guess that's exactly what you're seeing: Jetty picking up changes after Maven copies or compiles files. ;) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: running eclipse in production
Yes, I'm sure that's what he meant. Version 5.3 will turn off live class reloading in production, which is why he's saying you'll have to run in development mode. To clarify my original question (now that it's a dead horse)... I wasn't worried about reloading of the pages and other top-tier classes. They're already hot-reloading for me in production if I simply update the .class and .tml files. (I have the file-check-interval set to 60 seconds.) But the lower-level classes, not part of Tapestry's domain, don't reload. For example, I've got business logic in my domain objects, in a lower-level "model.jar". I've tried running with that jar exploded and updating the .class files but the changes don't get picked up. The eclipse maven plugin handles that for me in my development workspace, which is what sparked the question. On Mon, Oct 10, 2011 at 11:46 PM, Yohan Yudanara wrote: > Sorry, but the words "*turns off*" below should be "*turns on*", right? > Development mode will turn on live class reloading, right? > > CMIIW... > > On Tue, Oct 11, 2011 at 2:25 AM, Howard Lewis Ship > wrote: > > > 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). > > > > >
Re: running eclipse in production
Sorry, but the words "*turns off*" below should be "*turns on*", right? Development mode will turn on live class reloading, right? CMIIW... On Tue, Oct 11, 2011 at 2:25 AM, Howard Lewis Ship wrote: > 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). > >
Re: running eclipse in production
Also in your container you can set it up for debugging - i.e. attach to port number X, for debugging with eclipse. If that's what your intention was as well. On 11/10/2011, at 6:25 AM, Howard Lewis Ship wrote: > 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 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 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 > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: running eclipse in production
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 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 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
Re: running eclipse in production
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 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
running eclipse in production
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.
