On Mon, Jun 27, 2011 at 12:16 AM, laloluke <[email protected]> wrote: > Hello, > > The Release Notes 5.3 says that Reloading is disabled in production mode. > Actually we are working in a dynamic JAR loading without restarting the > server using one of the best features of Tapestry: Reloading. Obviously, we > prefer Tapestry rather than OSGi. > > The Reloading is disabled in production mode or has been permanently > removed? Is there any way to enable it? Would be nice that can enable or > disable (default option) Reloading in production mode. >
Are you sure you aren't relying on servlet container redeployment? Even with 5.2, bytecode changes inside JAR files would not be checked in production or development mode. If you are relying on servlet container redeployment (not a bad thing in production) then it should still work. More details, please. If you can make a sufficient case for, it would be possible to split the logic so that we could have a symbol to control dynamic reloading that's separate from tapestry.production-mode (but gets a default FROM tapestry.production-mode). > Thank you very much in advance. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-5-3-Reloading-in-Production-Mode-tp4527299p4527299.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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: [email protected] For additional commands, e-mail: [email protected]
