tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Troy <>
Subject Figuring out why Tomcat isn't serving a servlet (fwd)
Date Thu, 15 Nov 2001 20:00:31 GMT
Date: 18 Oct 2001 01:06:18 -0000
From: Dr. Evil <>
Subject: Figuring out why Tomcat isn't serving a servlet

I am completely stumped by a seemingly simple problem.  I have created
a very simple servlet:

import javax.servlet.*;
import javax.servlet.http.*;

public class hello extends HttpServlet {

       public void doGet(HttpServletRequest request,
       HttpServletResponse response)
       throws ServletException, IOException {

       PrintWriter out = response.getWriter();


I place compile and place it in

Then, with no problem, I can access it by going to

That's good.  Now I tried to add a web.xml file that will load up
another class which will create the database connection pool for me.
Here's what the web.xml file looks like:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"


Now with that file in place, I can no longer access servlet/hello.  I
tried putting in lines for the servlet:


but that didn't help either.  Is there a way to get this to work?
Connection pools aren't too useful if they're the only class you can
have on your server...

It seems that figuring out paths is a chronic difficulty with Tomcat.
Is there any way to debug what Tomcat is trying to do with a
particular request?


To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message