>> * Not having to modify server.xml directly. According to the
Tomcat
>> docs, you shouldn't modify this file.
> I think you may have misconstrued something in the docs. There's
> nothing wrong with modifying server.xml; for example, production
> environments must change it and web.xml to
> From: Gormley, Josh [mailto:[EMAIL PROTECTED]
> Subject: RE: Virtual Hosts [mostly solved]
>
> * Not having to modify server.xml directly. According to the Tomcat
> docs, you shouldn't modify this file.
I think you may have misconstrued something in the docs. T
> From: Mark Eggers [mailto:[EMAIL PROTECTED]
> Subject: RE: Virtual Hosts [mostly solved]
>
> For a root context, I usually set up an
> application.xml file in conf/Catalina// with
> the appropriate path="" in the Context element
That's incorrect for all rec
You may find that the default host loads all of the
web applications.
In order to solve this, make sure that each of the
contexts are not some subdirectory of another context.
You can use an absolute path to place this structure
outside of your Tomcat installation. For large
structures I th
With the help of several people on this list, I've been able to get my
server configured [mostly] the way I wanted it configured. Here's my
solution, hopefully it will be helpful to others
Goals:
* One instance of Tomcat running behind Apache
* Multiple VirtualHosts, each pointing to its own
