A Context's docBase can be anywhere, absolute or relative.
The disadvantage to absolute is you may run into OS issues, such as a docBase of "C:\webapps" not existing on a Solaris system. I'm sure the gurus can explain other disadvantages.
In my experience, the best thing to do is create separate appBase's for each Host, and then use a docBase relative to that appBase, with the appBase relative to CATALINA_HOME. Then it doesn't matter what OS you are running, as long as CATALINA_HOME and JAVA_HOME are set and you don't have problems with case-sensitivity, and you don't use symbolic links, your entire Tomcat hosting environment is essentially portable, server.xml and all.
John
On Thu, 26 Jun 2003 07:25:15 -0400, Mike Hulse <[EMAIL PROTECTED]> wrote:
I haven't read through all of the documentation yet, but while I was looking at the manager app and trying to understand how it works I noticed something. The manager app is not in /jakarta-tomcat-4.1.24/webapps. Instead there is a manager.xml that has a context <Context path="/manager" docBase="../server/webapps/manager" debug="0" privileged="true"> Does that mean if I put a app.xml in /jakarta-tomcat-4.1.24/webapps I can serve my app from directories other than /jakarta-tomcat-4.1.24/webapps? If so, are there any advantages or disadvantages of doing that?
Thanks, Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
