I can't say for monday but i hope in the week for the workflow if i understood you do:
-> webapp0 v0 -> webapp1 (with very few features) v0 -> remove webapp0 v0 -> webapp0 v1 this one works. If the remove phase is not done you have no guarantee at all (of course it can all be done the tomee running ;). *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/2/27 zeeman <[email protected]> > So next week Mon you think patch will be in? So I know when to ask QA to > test > again with Tomee snapshot. > > Thanks for the suggestion. > > I'm actually never deploying the same webapp war twice (different > versions). > There is always one webapp war, then I deploy a maintenance war (no EJBs > just a servlet filter) with a higher version as root context, so new users > get a message saying the site is under maintenance and it handles HTTP 503 > status for bots/search engines. > > When maintenance is done, a new webapp war is deployed and all previous > wars > are removed. I think this keep it simple and prevent issues you mentioned. > > Do you see anything wrong with this approach? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661050.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
