We have 2 live webapps running and we do not use or rely on live class reloading. Even more, i dont even have access or allowance to change a production website at runtime. Our policy is that everything needs to be tested and accepted before even going to production.
If something is wrong or needs to be changed i have to create a new version with the changes and this needs to be re-deployed. If this is not possible we shutdown the app instead of changing a production webapp. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Live-reload-in-production-tp4313825p4315096.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
