tomatically.
>
> Very nice from a maintenance and administration stand point.
>
> Negative: WL is expensive
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Upgrading-of-Wicket-application-on-server-without-losing-state-tp3965762p3974603
/Upgrading-of-Wicket-application-on-server-without-losing-state-tp3965762p3974603.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands
> 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 th
ing 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 ar
rently 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
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-uns
