Well contexts are used to name web applications web applications are accessed using http://host:port/contextName/
That is if you set context to 'clay', it's the expected behaviour it's accessible using http://host:port/clay/ For this, war is stored on server using name 'clay.war' If it was to be named 'example.war' then it would be accessible using http://host:port/example and it's context would be example, not clay. Am not sure why you want the war not be named with context name, as it's the expected behaviour of tomcat. Nehal Sangoi a écrit : >Hi All, > >I need to deploy only one warfile. e.g = "example.war" to multiple tomcat >instances having different context names. Currently, i am using ant's build >script with manager deployer. > >Hence, while deploying the warfile to multiple instances, in the "webapps" >of every instance, the war file's name gets changed to what the context name >is provided into the build script. > >This means, if i have a context named " clay " , then the existing warfile " >example.war " gets renamed to "clay.war" and gets deployed under the webapps >of clay tomcat instance. > >Kidnly, help me -- how can i configure manager deploy, for not having my >warfile name changed according to context detail. > > >Thanks & Regards, >Nehal > > > > >------------------------------------------------------------------------ > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
