> 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?
Well, if you put the Wicket session in the Http session (which is the default if I'm not mistaken) then e.g. Tomcat will serialize the sessions to disk on a controlled shutdown, and reread them on startup. Keep in mind serialVersionUID etc. Then the sessions becaome the responsibility of the container. - Tor Iver --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
