Hello list,
I use Tomcat 5.0.30 as a bare bones, no fuss webapp container, with a
very, very simple server.xml:
<Server port="8005" shutdown="SHUTDOWN">
<Service name="Catalina">
<Connector port="8009" protocol="AJP/1.3" enableLookups="false"
URIEncoding="UTF-8" maxProcessors="0"/>
<Engine name="Catalina" defaultHost="localhost">
<Host name="localhost" appBase="external-webapps" autoDeploy="false"
deployXML="false" unpackWARs="false">
<Context docBase="/var/lib/tomcat5/webapps/one2team" path="">
<!-- plus two loggers -->
</Context>
</Host>
</Engine>
</Service>
</Server>
We use mod_jk at the Apache level to communicate with the webapp.
Unfortunately, this configuration is a hack:
* the appBase in <Host> points to a non existing directory within
$CATALINA_HOME;
* the docBase of the only <Context> is an absolute path to the webapp root.
The problem is, we do _NOT_ want the webapp directory to be named
ROOT, we want it to remain one2team. And this is the only solution
I've found...
Ideally, I'd have liked to not lie to <Host> and have a ROOT.xml in
Catalina/localhost saying that no, my webapp root directory is not
named ROOT, it's one2team, thank you very much. But no, this doesn't
work.
As you can see, I also had to set autoDeploy to false, otherwise the
webapp was deployed twice: once under /, which is what we want, and
another time under /one2team, which we don't want either...
Does tomcat5.5 remove this limitation? Or even tomcat 6.x?
Thanks in advance,
--
Francis Galiegue, [EMAIL PROTECTED], [EMAIL PROTECTED]
One2team - 42 Av. Raymond Poincaré - 75116 PARIS
"When it comes to performance, weight is everything" - Tiff Needell
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
