Hi Yoav, Thanks for your ideas, but how do they work out in the ant deploy scenario, where the application actually resides in "/usr/local/tomcat/ work/Standalone/localhost/manager/forms.war" ?
*) Is it an option to create a symlink "forms" in the /webapps directory to point to "/usr/local/tomcat/work/Standalone/localhost/manager/forms.war "? *) Do I have any other options than creating a symlink? I'm working with a Windows-machine for development, so I'd prefer something not os-specific! *) The best thing would be a pseudo-context which simply points to another context, so each request gets mapped to the versioned context. thx alot Johannes "Shapira, Yoav" <[EMAIL PROTECTED]> 31.03.2003 16:51 Please respond to "Tomcat Users List" <[EMAIL PROTECTED]> To "Tomcat Users List" <[EMAIL PROTECTED]> cc Subject RE: Switching between releases during runtime Howdy, Several other approaches, all I think better than your context pointer idea: - Have the context XML definition file (tomcat 4.1 or later) name a symlink as the docBase. That symlink would point to myapp-1.0 and could be changed to myapp-1.1 etc. - Have the context entry itself in the webapps directory be a symlink to somewhere outside the webapps directory, for example: /local/build/myapp-1.0 /local/build/myapp-1.1 /local/tomcat/webapps/myapp -> /local/build/myapp-1.0 so "myapp" under webapps is just a symlink. - Just redeploy appropriately using the ant tasks supplied with tomcat an save yourself headaches in the long run. Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Saturday, March 29, 2003 12:33 PM >To: Tomcat Users List >Subject: Switching between releases during runtime > >hi there, > >Is it possible to have a "virtual" context, which just points to another >context? >e.g. >myapp = current version, should point to myapp-1.0 >myapp-1.0 >myapp-1.1 > >Is it possible to change the context "myapp" is pointing to during >runtime? >This would make switching between releases much easier rather than having >to redeploy for each release switch. > >What do you think about this idea? > >thx >Johannes This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]