Hi Chris,
Tomcat should recognize "/servlet/briefXSL" without the explicit
servlet-mapping you are using -- but I don't know if that is what's causing
your problem. For all my servlets, I have the following type of entry:
<servlet>
<servlet-name>briefXSL</servlet-name>
<servlet-class>com.smartbrief.BriefXSL.Servlet</servlet-class>
</servlet>
The default Invoker automatically sets up "/servlet/" as a mapping for all
your defined servlets. So, the above should be enough to get
"/servlet/briefXSL" to pull up correctly -- without the servlet-mapping you
have below. Maybe the explicit servlet-mapping you are doing is somehow
messing with the default Invoker on Linux, but that's only speculation...
Thanks,
--jeff
----- Original Message -----
From: "Chris McNeilly" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 31, 2001 1:15 PM
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
>
