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 <yohan.yudan...@gmail.com>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 <hls...@gmail.com> > 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). > > > > >
