aversion = downtime of a heavily used production system.
best avoided if possible.
thx.
On 12/07/2012 9:47 AM, Lenny Primak wrote:
I don't think it's possible. Tapestry does not track file changes in production
mode.
What's your aversion to redeployment? For example, if you use glassfish, you
can save session state across redeployment. Don't know if other containers
support this but they should.
On Jul 11, 2012, at 7:14 PM, Paul Stanton <p...@mapshed.com.au> wrote:
is there a way to force the global messages catalog to be reloaded while
running in production mode?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
