|
I have st.Servlet1 class on Tomcat
4.1/weapps/Myapp/WEB-INF/classes/st
and Servlet1.shtml on Tomcat
4.1/weapps/Myapp
I have not problen when call Servlet1.shtml whit http://localhost:8080/Myapp/Servlet1.shtml
but when I click on button to call
Servlet1.class (the servlet) Tomcat return 404 error..
What is a problem ???
I send Myapp/WEB-INF Web.xml and
Myapp/Servlet1.shtml to you see if I have any wrong.
Thank for your help !!!!!
Andres.
|
Servlet1.shtml
Description: Binary data
<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd";> <web-app> <!-- General description of your web application -->
<display-name>Un servlet simple</display-name> <description> Se trata de poner
un servlet en el tomcat. El servlet es simple. </description> <!-- Context initialization parameters that define shared
String constants used within your application, which
can be customized by the system administrator who is
installing your application. The values actually
assigned to these parameters can be retrieved in a
servlet or JSP page by calling:
String value =
getServletContext().getInitParameter("name");
where "name" matches the <param-name> element of
one of these initialization parameters.
You can define any number of context initialization
parameters, including zero.
--> <context-param> <param-name>webmaster</param-name> <param-value>[EMAIL PROTECTED]</param-value>
<description> The EMAIL address of the administrator to whom questions and comments
about this application should be addressed. </description> </context-param> <!-- Servlet definitions for the servlets that make up
your web application, including initialization
parameters. With Tomcat, you can also send requests
to servlets not listed here with a request like this:
http://localhost:8080/{context-path}/servlet/{classname}
but this usage is not guaranteed to be portable. It also
makes relative references to images and other resources
required by your servlet more complicated, so defining
all of your servlets (and defining a mapping to them with
a servlet-mapping element) is recommended.
Servlet initialization parameters can be retrieved in a
servlet or JSP page by calling:
String value =
getServletConfig().getInitParameter("name");
where "name" matches the <param-name> element of
one of these initialization parameters.
You can define any number of servlets, including zero.
--> <servlet> <servlet-name>Servlet1</servlet-name> <description> el
servlet sencillo... </description> <servlet-class>st.Servlet1</servlet-class>
<!-- Load this servlet at server startup time --> <load-on-startup>1</load-on-startup>
</servlet> <!-- Define mappings that are used by the servlet container to
translate a particular request URI (context-relative) to a
particular servlet. The examples below correspond to the
servlet descriptions above. Thus, a request URI like:
http://localhost:8080/{contextpath}/graph
will be mapped to the "graph" servlet, while a request like:
http://localhost:8080/{contextpath}/saveCustomer.do
will be mapped to the "controller" servlet.
You may define any number of servlet mappings, including zero.
It is also legal to define more than one mapping for the same
servlet, if you wish to.
--> <servlet-mapping> <servlet-name>Servlet1</servlet-name> <url-pattern>/st</url-pattern>
</servlet-mapping> <!-- Define the default session timeout for your application,
in minutes. From a servlet or JSP page, you can modify
the timeout for a particular session dynamically by using
HttpSession.getMaxInactiveInterval(). --> <session-config> <session-timeout>30</session-timeout>
<!-- 30 minutes --> <servlet><servlet-name></servlet-name><servlet-class> </servlet-class>
</servlet> </session-config> </web-app>
-- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
