By nightmare I meant complexity. Currently all my webapps are located in a single directory, its flat, it only contains webapps (IE. folders with a WEB-INF directory). I have approximately a dozen Hosts defined across 3 domain names (and every intention of adding more). Some Hosts have single Contexts, but others have dozens of Contexts defined. If each Host must have it's own unique appBase for the Manager to work correctly, then that entails a 3 level structure for my webserver's document root: / --/webapps -----/host_<MY_HOST> -------/<MY_CONTEXT>
Which means reworking the build scripts for each and every webapp. If this is the only way to have the manager work correctly, then I guess I'll have to do. I just don't understand why the server.xml cannot be interpreted as a logical structure. If I can define a "/blahblah" Context on a docBase of "foobar-webapp" (a logical or arbitrary mapping) why can't Contexts be understood as belonging to certain arbitrary Hosts, regardless of their filepath? On Mon, Nov 2, 2009 at 12:11 PM, Hassan Schroeder < hassan.schroe...@gmail.com> wrote: > On Mon, Nov 2, 2009 at 9:22 AM, Jonathan Mast > <jhmast.develo...@gmail.com> wrote: > > So you are saying each Host *must* have it's own distinct appBase. > > Not "must", but that's the easy/simple/standard way to do it, and of > course you're free to complicate your life in any number of ways by > fighting it. :-) > > > That > > sucks, doing that will make my deployment process a nightmare. Any way > > around the problem I described above? > > Uh, "nightmare"? If it were me I'd fix that deployment process. YMMV. > > -- > Hassan Schroeder ------------------------ hassan.schroe...@gmail.com > twitter: @hassan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
