Hi guys, I was wondering about the following standard scenario: - application v0.1 deployed to your favorite servlet container - you want to deploy version v0.2 with minimal downtime and without losing any session state (because it's a web shop application for example)
Is there a convenient way to shut down a wicket application so that it saves its complete state to e.g. the filesystem and the next wicket app that boots up initially reads the state from those files? anyone else handling server upgrades differently and in a better way? Thanks! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Upgrading-of-Wicket-application-on-server-without-losing-state-tp3965762p3965762.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
