You have the choice of starting with the simple approach to
get things working, which is to map all requests for a webapp
to Tomcat. This is the approach used in Tomcat 3.3 for the
default auto-generated mod_jk.conf. It is accomplished using
configuration lines like:
JkMount /myapp ajpxx
JkMount /myapp/* ajpxx
You lose in performance, but gain in having web.xml configured
behavior work automatically.
The potentially much more challenging approach is to try
to have Apache serve static resources. This is the approach
used in Tomcat 3.3 in the auto-generated mod_jk.conf with
forwardAll="false" and the approach always used in Tomcat 3.2.x.
Instead of mapping all requests for a webapp to Tomcat, you
start out with just:
JkMount /myapp/servlet/* ajpxx
JkMount /myapp/*.jsp ajpxx
You then add Apache <Alias> and <Directory> directives
to allow Apache to serve the static resources, for example:
Alias /myapp "<path to myapp>"
<Directory "<path to myapp>">
Options Indexes FollowSymLinks
</Directory>
This may be what you are looking for to have Apache serve
HTML.
You then continue adding to the Apache configuration to
duplicate any additional configuration in your web.xml,
if possible. Tomcat 3.3 automates some of this in its
auto-generated mod_jk.conf, including servlet mappings
and welcome files.
Hope this helps.
Cheers,
Larry
> -----Original Message-----
> From: Mike Kelley [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 04, 2001 5:11 PM
> To: [EMAIL PROTECTED]
> Subject: HTML under mod_jk
>
>
> I gave up on mad_webapp put in mod_jk .... How do I get TC/mod_jk to
^^^ interesting typo :)
> recognize *.html pages within an webapp???
>
> --
> To unsubscribe: <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
