I believe your approach is the correct one. The context name is part of how isapi_redirect.dll determines which requests to forward to Tomcat, i.e. the mappings in uriworkermap.properties always start with a "/". I don't think mapping just "*.jsp" is supported.
Cheers, Larry > -----Original Message----- > From: Terrence Beard [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 08, 2002 11:23 AM > To: Tomcat-User (E-mail) > Subject: Contexts in Tomcat 3.2.1 - Necessary? > > > Hello all! > > Here's what we've got: WinNT 4SP6 running IIS 4. We support > several seperate > web sites via IIS (couple internal, several external). The > source for each > is kept on a seperate directory path, different from the > Tomcat install > path. The JSP pages are being serviced by Tomcat 3.2.1 via the > isapi_redirect.dll, which is set on the filter list for the > "machine" (as > opposed to each web site). > > In order to get things to work, we needed to define a > seperate context for > each site in the server.xml file, and reference them in the > uriworkmap.properties file. So, there a context named "foo" > pointing as the > JSP source directory for the www.foo.com. On the URL, these files are > accessed (and processed) via www.foo.com/foo/sample.jsp. > > The question is this: is this the proper way to do this, or is there a > better/preferred way of doing this? Is there a way to say > "process JSP files > no matter where you find them" without being determential?! > > All suggestions are welcome and appreciated! > > Thanks! > > Terry Beard > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
