• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

updating web app

 
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear guys,
I've added features and fixes to my web app which works well in the development environment, want to deploy it to production environment where users are logged on, have planned like this and would like to know if this could be a well-working strategy: When I update the web archive and deploy a new version to the app server (Tomcat 5.5) I set it to /context2 so everything still works normal from the usual /context1?
When the new tests work you deploy again and replace /context1, or change the links from / so everything points to /context2 and next deployment you replace /context1 accordingly. This way you'd be able to test the new verison once more in production environemnt with not logging off all users.
Thank you
Niklas R

[ April 16, 2008: Message edited by: Niklas Rosencrantz ]
[ April 16, 2008: Message edited by: Niklas Rosencrantz ]
 
reply
    Bookmark Topic Watch Topic
  • New Topic