> >For example, mod_jk won't know that we want
> >Tomcat to process a filter chain against a directory unless we've done a
> >JkMount for that tree, whereas it would know that Tomcat needs to process
a
> >JSP page. On the other hand, mod_webapp would know about the filter
chain
> >because the resources would have been deployed as part of a web app.
> This isn't quite true. You can get the same functionality with mod_jk as
> mod_webapp by saying:
> JkMount /mycontext ajp13
> JkMount /mycontext/* ajp13
> that works *exactly* the same as:
> WebAppDeploy mycontext warpConnection /mycontext/
Which part of "unless we've done a JkMount for that tree" didn't you
understand? I did not say that mod_jk doesn't support the facility, just
that it has to be configured properly. Your example provides exactly what I
said would be necessary.
Having done this, Tomcat will serve up even static resources in that
context. Which is what the deployment is asking for in this case.
--- Noel
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
