Excuse me asking, but with class reloading disabled in production, template reloading still works, correct?
My designer who mostly does TML's expects templates be reloadable in production. Adam PS. On a side note, what about a hybrid switch? Like component class reloading but disable service reloading? On Tue, Apr 19, 2011 at 6:14 PM, Howard Lewis Ship <hls...@gmail.com> wrote: > On Tue, Apr 19, 2011 at 4:00 PM, Igor Drobiazko > <igor.drobia...@gmail.com> wrote: >> I never used live reloading in production, but it might be a cool marketing >> weapon. We could promote it as seomthing similar to ZeroTurnaround's >> LiveRebel: >> >> http://www.zeroturnaround.com/liverebel/ >> >> Imagine a new slogan on Tapestry's webpage: "With Tapestry you can roll out >> and roll back changes to live applications instantly - without Downtime" > > I don't like to over-promise. Live reloading has some limitations in > terms of reloading of service layer objects. I think having a seamless > redeploy model is for the application servers to handle, not the > framework. > > Basically, in production, you want to hype "fast and stable". In > development you want to hype, "agile and testable." > >> >> On Tue, Apr 19, 2011 at 7:11 PM, Howard Lewis Ship <hls...@gmail.com> wrote: >> >>> Out of curiosity ... does anyone out there rely on live class >>> (template, message catalog, whatever) reloading in their live, >>> production application? Now, normally, I'd think not, because the >>> deployed app will be packaged in a WAR and the unit of redeployment is >>> the entire WAR ... but I suppose some people could be using the >>> "exploded WAR" format, which would allow classes and templates to be >>> updated while the application runs. >>> >>> Live reloading is a feature that was originally intended for >>> development only; Tapestry 5.2 supports live reloading in the live >>> application, but as of yesterday, Tapestry 5.3 does NOT. I'm hoping to >>> see some improvements in throughput and a reduction in memory >>> utilization in production applications ... but it's not too late to >>> shift things so that 5.3 can support production reloading as well. >>> I'd prefer not to, however. >>> >>> -- >>> 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 >>> >>> >> >> >> -- >> Best regards, >> >> Igor Drobiazko >> http://tapestry5.de >> > > > > -- > 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
