This is a guess, but have you disabled the servlet invoker in the
server.xml file? I believe that the servlet invoker will grab the request
for /servlet/* before the webapp will check its mappings. I would suggest
removing the servlet invoker from your server.xml file and see if this
works. If so, then you'll need to decide if you need it and need to change
your servlet's mapping or if you can get along just fine without it.
(Remember that this is a server-wide setting).
Randy
> -----Original Message-----
> From: Chris McNeilly [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 31, 2001 4:15 PM
> To: [EMAIL PROTECTED]
> Subject: How to debug a missing servlet error?
>
>
> Hi,
>
> I have a development environment that works correctly (Win
> 98), but when
> I move the code over to my QA environment (Linux) tomcat can no longer
> find the servlet. I have a web.xml file in the Web-Inf directory that
> has the following:
>
> <web-app>
> <servlet>
> <servlet-name>
> briefXSL
> </servlet-name>
> <servlet-class>
> com.smartbrief.BriefXSLServlet
> </servlet-class>
> </servlet>
> <servlet-mapping>
> <servlet-name>briefXSL</servlet-name>
> <url-pattern>/servlet/briefXSL</url-pattern>
> </servlet-mapping>
>
> </web-app>
>
> Tomcat receives the request from apache, but doesn't know what to do
> with it and spits back a 404. It's almost as if tomcat isn't reading
> the web.xml file at all.
>
> Thanks,
>
> Chris
>
