"Craig R. McClanahan" wrote:
> As a general note, Tomcat 4 uses a validating XML parser when reading
> web.xml files, to help you ensure that your web apps will be portable to
> any container. A consequence of this is that you must follow the element
> ordering requirements in the DTD *exactly*. Tomcat 3.2 did not do a
> validating parse, so it accepted invalid web.xml files.
This is probably the problem - in the root web.xml load-on-startup was
last, and in the stuff supplied to me load-on-startup was first.
Having fixed this though a new problem has arisen:
I'm getting this in the logfile suddenly:
2001-09-21 12:27:21 StandardWrapper[:jsp]: Using Jasper classloader for
servlet jsp
2001-09-21 12:27:21 StandardWrapper[:jsp]: Marking servlet jsp as
unavailable
2001-09-21 12:27:21 StandardContext[]: Servlet threw load() exception
javax.servlet.ServletException: Class
org.apache.jasper.servlet.JspServlet is not a Servlet
[snip]
2001-09-21 12:56:18 StandardWrapper[/thh:feersum]: Marking servlet
feersum as unavailable
2001-09-21 12:56:18 StandardContext[/thh]: Servlet /thh threw load()
exception
javax.servlet.ServletException: Class
com.bitr8.feersumenjin.control.web.MainServlet is not a Servlet
[snip]
I understood from the docs that Tomcat v4.0 was backwards compatible -
yet it complains that all of the servlets it's supposed to run are not
servlets - does this make sense to anyone? Is there something missing
that I should be configuring?
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
S/MIME Cryptographic Signature
