Hi Howard,
Maybe the question should really be: Does anyone out there rely on live class (template, message catalog, whatever) reloading in their live, production application? .... and what critical benefit does this offer? I am with you on the paradox of choice. When I roll out new versions, there are usually db schema and directory structure changes not just UI changes. So the roll out has to have the server brought down. I would love to have an atomic updating service. A new war is placed in a staging location. The db update magically happens and then the older server is brought down and replaced with the new server. But absence this magical update genie, I would prefer the performance improvements because that will be useful every day. For those who feel that they need this, is there any sort of hooking that a side project could use to restore this functionality without impact the people who rather take the benefits of not having dynamic class loading in production? Or maybe they just run in development mode on the production box? ( maybe silly statement - but we are still on T4 :-( ) Patrick Moore Amplafi http://amplafi.com mobile: 650-207-9792 "Put your front window on your front page" personal blog : http://sworddance.com/blog On Tue, Apr 19, 2011 at 10:11 AM, 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 > >
