I'm not sure what you are after. But... You could put Apache in front of Tomcat. Have Apache mount the appropriate Tomcat apps so that you would be able to type in.
http://mycompany.com/firstapp Or you could setup a Virtual Host for each time you wanted to do: http://firstapp.mycompany.com/ It may not be that much different but it does mean you don't have to touch Tomcat configuration when deploying, just Apache. Oscar On Thu, 29 Jan 2004, Kal Govindu wrote: > Hi all, > > Our company has just started into Java based web applications. Our > current methodology for deploying to production is to setup a DNS like > say > firstapp.mycompany.com and define a <Host> entry in the server.xml with > aliases to respond to the new DNS. We do this purely for the capability > of typing http://firstapp.mycompany.com in a web browser and getting to > the application. > > But this is kind of cumbersome and time consuming setup when ever we > deploy to production. As we have more applications this way we will end > up with several <Host>'s which does not seem like a good thing. Is there > a better way to do this? > > Please help. Thanks > Kal > > > --------------------------------------------------------------------- > 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]
