We are using Weblogic 10.3 and it has a nice feature that allows two versions of the app to run concurrently.
What happens is this: - V1 is running and sessions are currently active - deploy V2 - existing V1 sessions will continue to use V1 code - new request (i.e. new session) will use V2 This is OOTB nothing needed on our code or configuration. No need to bring down an app or server or cluster. Happens automatically. 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.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
