On Wed, Apr 20, 2011 at 1:36 AM, Howard Lewis Ship <hls...@gmail.com> wrote:
> On Tue, Apr 19, 2011 at 4:22 PM, Adam Zimowski <zimowsk...@gmail.com> wrote: >> 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. >> > > Well, then, you're screwed in Tapestry 5.3 :-) Looks like we'll > probably have to introduce a new symbol to allow this to be enabled in > production. But I think the vast majority of deployments will not need > this (and may like the increased throughput and lowered memory > utilization). I'm on the screwed side of the moon too. I've never planned to use it in production but happened. We discovered a bug in a decision-maker point of the app business and fortunately we had the exploded jar so we simply swapped the bugged class with the fixed one and all was solved and everyone happy. Quick fix is a big win here. After that even I've always kept that feature in mind when plan deploy... Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
