Go back to first prinicples. Try accessing the servlet directly via tomcat
rather than worying about apache - try looking at
http://youmachine:8080/yourcontext/servlet/YourServlet
The port 8080 reefres to the port tomcat is running on. With no port
specified, it means you are trying to access via the standard http port of
80, which is where Apache (or some other webserver) is running.
If that works, its an Apache/mod_jk issue. If not, its a web.xml issue. Just
to reassure you, tomcat does work - I wouldn't be at all suprised if it has
the largest user base of all servlet engines currently on the market.
If you find that doesn't work, please post your web.xml so we can have a
look. If not, can you post the directives you use to get Apache running with
mod_jk (probably the mod_jk.conf-auto file generated in tomcat/conf).
regards,
sam
----- Original Message -----
From: "Dan & Sharon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 23, 2001 6:55 PM
Subject: seems as though a servlet engine would have a little clearer
documentation on getting servlets running
> ok,
> install tomcat,
> jsps are workin,
> made new context,
> jsps are workin in it,
> write a servlet(5 min),
> try to get servlet working(5 hr),
> read documentation,
> it says put servlets in WEB-INF/classes dir, did that
> it says add servlet to WEB-INF/web.xml, did that
> <web-app>
> <servlet>
> <servlet-name>servtest.class</servlet-name>
> <servlet-class>servtest.class</servlet-class>
> </servlet>
> </web-app>
> restart tomcat(can't believe this has to be done everytime a servlet
> gets added or changed), did that
> it says call your servlet with
> "http://thehost/WEB-APP/servlet/theservletname";
> did that
> response: 404
> there's no servlet directory, kinda makes sense, but i thought mod_jk
> was taking care of that. HMM.
> so now that i've followed the instructions and that didn't work, i make
> a servlet directory and add my servlet there. web browser tries to
> download and save it to my disk, no display.
> i'm sure that this being a servlet engine, it would probably serve
> servlets, otherwise that would be really embarrasing for the
> programmers, so, anyone got any suggestions?
>
>
