Ok, your answer just recaps everything that is needed to run
Apache-jk_mod-Tomcat but does not answer my question. What if in your
setting, you have set Context path, what would be the consequences?
How are the servlets then are accessed? Is it required to include
Context path in the uri ending to the servlet like the examples are
provided earlier? It seems like that is not the case so I am taking it
either Context path, if it's designated, has no bearing when it comes
to jk_mod or must be included in the uri in some other way.
On 8/19/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
/*httpd.conf
JkMount maps all JSP (*.jsp) to ajp13
*/
e.g.
httpd.conf
JkMount /*.jsp ajp13
/*map ajp13 to your webapp docRoot /var/tomcat4/webapps/domain1
<VirtualHost *>
ServerName domain1.com
ServerAlias www.domain1.com
DocumentRoot /var/tomcat4/webapps/domain1
JkMount /* ajp13
</VirtualHost>
/*server.xml maps known webapp docBase /var/tomcat4/webapps/domain to domain
name(domain1) via this entry*/
<Host name="domain1.com" debug="0" appBase="webapps" unpackWARs="true">
<Alias>www.domain1.com</Alias>
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="virtual_log1." suffix=".log" timestamp="true"/>
<Context path="" docBase="/var/tomcat4/webapps/domain1" debug="0"
reloadable="true"/>
</Host>
HTH
M-
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
