Yup. Tomcat 3.3 has the Invoker enabled by default (although 3.3 doesn't have a global web.xml file, so it's declared in server.xml :).
"Drew Jorgenson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Looks like the invoker servlet is being used, which is declared in the > global web.xml file. The <servlet-name> and <servlet-class> that you see > are used to map a name to a servlet, which are all accessed through > /servlet/* > > Drew. > > On Tue, 2005-02-22 at 10:43, Beckle, Steven R wrote: >> I'm currently working on a legacy Tomcat 3.3 project that was developed >> (not by me) a couple of years ago, and I am having a heck of a time >> understanding how servlets are getting mapped properly. A typical URL in >> the application is of the form CONTEXT/servlet/servletName - nothing >> fancy there. However, the webapp's web.xml file contains no >> <servlet-mapping> tags, but just the <servlet-name> and <servlet-class> >> tags. Is there another way in Tomcat to map URL's to servlets, either >> through a server configuration setting or some other "global" >> information contained in a conf/xml file that I'm not aware of? My >> problem isn't that the servlets aren't being accessed - they display >> content fine. I'm for now just trying to understand how Tomcat is >> associating the URL string with the actual servlet class since there is >> no servlet mapping being done in the web.xml file. >> >> >> >> The servlets themselves reside in jar files under CONTEXT/WEB-INF/lib. >> >> >> >> Thank you. >> >> >> >> Steve Beckle >> Computer Associates >> tel: +1 (630) 505 6855 >> >> fax: +1 (630) 505 6983 >> >> [EMAIL PROTECTED] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
