Richard,
sorry for the latency here... our connection is proving a right pain...
On Wed, 27 Jun 2001 01:19, Richard Richter wrote:
> Here (you wrote similar advice "Re: Servlet configuration" to somebody
> else) I looked to web.xml, which contains:
>
> <servlet>
> <servlet-name>Hello</servlet-name>
> <servlet-class>Hello</servlet-class>
> </servlet>
>
> <servlet>
> <servlet-name>HelloServlet</servlet-name>
> <servlet-class>Hello</servlet-class>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>HelloServlet</servlet-name>
> <url-pattern>/hello</url-pattern>
> </servlet-mapping>
>
did I write that? shit. there should only be one <servlet> ... </servlet>
entry per servlet _name_ (although you can deploy the same servlet class as
different servlets and use different parameters to achieve different
behaviour). So if you remove the first of the two <servlet> ... </servlet>
entries it would be correct.
> Maybe there is some redundancy or missing... but where? Because Hello.class
> is in webapps/intranet/WEB-INF/classes (with all classes generated from
> jsps) and web.xml is in WEB-INF... that's right I hope. URI is still the
> same:
[sidenote] the JSPs get compiled in the $TOMCAT_HOME/work directory, unless
you're compiling them yourself (which I dont think there's any reason to)
they shouldn't be in the WEB-INF/classes directory.
> host:port/intranet/servlet/hello
ok - I'm a bit frazzled here because its been a while since I last wrote
about this, so let me refresh my mind...
I'm assuming you have tomcat available as well? Assuming you're running both
on the same box... can you request
http://localhost:8080/intranet/servlet/hello (straight through tomcat).
When I get frustrated I do a "tail -f logs/*" and see if that helps me (o:
not sure if that'll be any help... anyway I think the approach should first
be to check that everything is working in standalone.
cheesr
dim
