web/WEB-INF/web.xml

<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE web-app (View Source for full doctype...)>
<web-app>
  <!-- General description of your web application -->
  <display-name>My Web Application</display-name>
  <description>This is version 0.1 of my application</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 nymber of context initialization
    parameters, including zero.
  -->
  <context-param>
    <param-name>webmaster</param-name>
    <param-value>eax@fukt.bth.se</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>controller</servlet-name>
    <description>This servlet plays the "controller" role in the MVC archiecture...</description>
    <servlet-class>com.mycompany.myPackage.ControllerServlet</servlet-class>
    <init-param>
      <param-name>listOrders</param-name>
      <param-value>com.mycompany.myactions.ListOrdersAction</param-name>
    </init-param>
    <init-param>
      <param-name>saveCustomer</param-name>
      <param-value>com.mycompany.myactions.SaveCustomerAction</param-value>
    </init-param>
    <!-- Load this servlet at server startup time -->
    <load-on-startup>5</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 correspont 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>controller</servlet-name>
    <url-pattern>*.do</url-pattern>
  </servlet-mapping>
  <servlet-mapping>
    <servlet-name>graph</servlet-name>
    <url-pattern>/graph</url-pattern>
  </servlet-mapping>
  <!--
    Define the default session timeout for your application,
    in minutes. From a servlet or a 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 -->
  </session-config>
</web-app>
1	eax	1.1	<?xml version="1.0" encoding="ISO-8859-1" ?>
2			<!DOCTYPE web-app (View Source for full doctype...)>
3			<web-app>
4			<!-- General description of your web application -->
5			<display-name>My Web Application</display-name>
6			<description>This is version 0.1 of my application</description>
7			<!--
8			Context initialization parameters that define shared
9			String constants used within your application, which
10			can be customized by the system administrator who is
11			installing your application. The values actually
12			assigned to these parameters can be retrieved in a
13			servlet or JSP page by calling:
14
15			String value =
16			getServletContext().getInitParameter("name");
17
18			Where "name" matches the <param-name> element of
19			one of these initialization parameters.
20
21			You can define any nymber of context initialization
22			parameters, including zero.
23			-->
24			<context-param>
25			<param-name>webmaster</param-name>
26			<param-value>eax@fukt.bth.se</param-value>
27			<description>The email address of the administrator to whom questions and comments about this application should be addressed.</description>
28			</context-param>
29			<!--
30			Servlet definitions for the servlets that make up
31			your web application, including initialization
32			parameters. With Tomcat, you can also send requests
33			to servlets not listed here with a request like this:
34
35			http://localhost:8080/{context-path}/servlet/{classname}
36
37			but this usage is not guaranteed to be portable. It also
38			makes relative references to images and other resources
39			required by your servlet more complicated, so defining
40			all of your servlets (and defining a mapping to them with
41			a servlet-mapping element) is recommended.
42
43			Servlet initialization parameters can be retrieved in a
44			servlet or JSP page by calling:
45
46			String value =
47			getServletConfig().getInitParameter("name");
48
49			where "name" matches the <param-name> element of
50			one of these initialization parameters.
51
52			You can define any number of servlets, including zero.
53			-->
54			<servlet>
55			<servlet-name>controller</servlet-name>
56			<description>This servlet plays the "controller" role in the MVC archiecture...</description>
57			<servlet-class>com.mycompany.myPackage.ControllerServlet</servlet-class>
58			<init-param>
59			<param-name>listOrders</param-name>
60			<param-value>com.mycompany.myactions.ListOrdersAction</param-name>
61			</init-param>
62			<init-param>
63			<param-name>saveCustomer</param-name>
64			<param-value>com.mycompany.myactions.SaveCustomerAction</param-value>
65			</init-param>
66			<!-- Load this servlet at server startup time -->
67			<load-on-startup>5</load-on-startup>
68			</servlet>
69			<!--
70			Define mappings that are used by the servlet container to
71			translate a particular request URI (context-relative) to a
72			particular servlet. The examples below correspont to the
73			servlet descriptions above. Thus, a request URI like:
74
75			http://localhost:8080/{contextpath}/graph
76
77			will be mapped to the "graph" servlet, while a request like:
78
79			http://localhost:8080/{contextpath}/SaveCustomer.do
80
81			will be mapped to the "controller" servlet.
82
83			You may define any number of servlet mappings, including zero.
84			It is also legal to define more than one mapping for the same
85			servlet, if you wish to.
86			-->
87			<servlet-mapping>
88			<servlet-name>controller</servlet-name>
89			<url-pattern>*.do</url-pattern>
90			</servlet-mapping>
91			<servlet-mapping>
92			<servlet-name>graph</servlet-name>
93			<url-pattern>/graph</url-pattern>
94			</servlet-mapping>
95			<!--
96			Define the default session timeout for your application,
97			in minutes. From a servlet or a JSP page, you can modify
98			the timeout for a particular session dynamically by using
99			HttpSession.getMaxInactiveInterval().
100			-->
101			<session-config>
102			<session-timeout>30</session-timeout>
103			<!-- 30 minutes -->
104			</session-config>
105			</web-app>