https://wiki.twig.es/index.php?action=history&feed=atom&title=Basic_tomcat_web.xml_fileBasic tomcat web.xml file - Revision history2026-05-06T13:10:42ZRevision history for this page on the wikiMediaWiki 1.23.0https://wiki.twig.es/index.php?title=Basic_tomcat_web.xml_file&diff=3449&oldid=prevGeorge2: Created page with "<source lang="text"> <?xml version="1.0" encoding="ISO-8859-1"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. S..."2016-07-01T14:08:39Z<p>Created page with "<source lang="text"> <?xml version="1.0" encoding="ISO-8859-1"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. S..."</p>
<p><b>New page</b></p><div><source lang="text"><br />
<?xml version="1.0" encoding="ISO-8859-1"?><br />
<!--<br />
Licensed to the Apache Software Foundation (ASF) under one or more<br />
contributor license agreements. See the NOTICE file distributed with<br />
this work for additional information regarding copyright ownership.<br />
The ASF licenses this file to You under the Apache License, Version 2.0<br />
(the "License"); you may not use this file except in compliance with<br />
the License. You may obtain a copy of the License at<br />
<br />
http://www.apache.org/licenses/LICENSE-2.0<br />
<br />
Unless required by applicable law or agreed to in writing, software<br />
distributed under the License is distributed on an "AS IS" BASIS,<br />
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.<br />
See the License for the specific language governing permissions and<br />
limitations under the License.<br />
--><br />
<br />
<!DOCTYPE web-app<br />
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"<br />
"http://java.sun.com/dtd/web-app_2_3.dtd"><br />
<br />
<web-app><br />
<br />
<br />
<!-- General description of your web application --><br />
<br />
<display-name>My Web Application</display-name><br />
<description><br />
This is version X.X of an application to perform<br />
a wild and wonderful task, based on servlets and<br />
JSP pages. It was written by Dave Developer<br />
(dave@mycompany.com), who should be contacted for<br />
more information.<br />
</description><br />
<br />
<br />
<!-- Context initialization parameters that define shared<br />
String constants used within your application, which<br />
can be customized by the system administrator who is<br />
installing your application. The values actually<br />
assigned to these parameters can be retrieved in a<br />
servlet or JSP page by calling:<br />
<br />
String value =<br />
getServletContext().getInitParameter("name");<br />
<br />
where "name" matches the <param-name> element of<br />
one of these initialization parameters.<br />
<br />
You can define any number of context initialization<br />
parameters, including zero.<br />
--><br />
<br />
<context-param><br />
<param-name>webmaster</param-name><br />
<param-value>myaddress@mycompany.com</param-value><br />
<description><br />
The EMAIL address of the administrator to whom questions<br />
and comments about this application should be addressed.<br />
</description><br />
</context-param><br />
<br />
<br />
<!-- Servlet definitions for the servlets that make up<br />
your web application, including initialization<br />
parameters. With Tomcat, you can also send requests<br />
to servlets not listed here with a request like this:<br />
<br />
http://localhost:8080/{context-path}/servlet/{classname}<br />
<br />
but this usage is not guaranteed to be portable. It also<br />
makes relative references to images and other resources<br />
required by your servlet more complicated, so defining<br />
all of your servlets (and defining a mapping to them with<br />
a servlet-mapping element) is recommended.<br />
<br />
Servlet initialization parameters can be retrieved in a<br />
servlet or JSP page by calling:<br />
<br />
String value =<br />
getServletConfig().getInitParameter("name");<br />
<br />
where "name" matches the <param-name> element of<br />
one of these initialization parameters.<br />
<br />
You can define any number of servlets, including zero.<br />
--><br />
<br />
<servlet><br />
<servlet-name>controller</servlet-name><br />
<description><br />
This servlet plays the "controller" role in the MVC architecture<br />
used in this application. It is generally mapped to the ".do"<br />
filename extension with a servlet-mapping element, and all form<br />
submits in the app will be submitted to a request URI like<br />
"saveCustomer.do", which will therefore be mapped to this servlet.<br />
<br />
The initialization parameter names for this servlet are the<br />
"servlet path" that will be received by this servlet (after the<br />
filename extension is removed). The corresponding value is the<br />
name of the action class that will be used to process this request.<br />
</description><br />
<servlet-class>com.mycompany.mypackage.ControllerServlet</servlet-class><br />
<init-param><br />
<param-name>listOrders</param-name><br />
<param-value>com.mycompany.myactions.ListOrdersAction</param-value><br />
</init-param><br />
<init-param><br />
<param-name>saveCustomer</param-name><br />
<param-value>com.mycompany.myactions.SaveCustomerAction</param-value><br />
</init-param><br />
<!-- Load this servlet at server startup time --><br />
<load-on-startup>5</load-on-startup><br />
</servlet><br />
<br />
<servlet><br />
<servlet-name>graph</servlet-name><br />
<description><br />
This servlet produces GIF images that are dynamically generated<br />
graphs, based on the input parameters included on the request.<br />
It is generally mapped to a specific request URI like "/graph".<br />
</description><br />
</servlet><br />
<br />
<br />
<!-- Define mappings that are used by the servlet container to<br />
translate a particular request URI (context-relative) to a<br />
particular servlet. The examples below correspond to the<br />
servlet descriptions above. Thus, a request URI like:<br />
<br />
http://localhost:8080/{contextpath}/graph<br />
<br />
will be mapped to the "graph" servlet, while a request like:<br />
<br />
http://localhost:8080/{contextpath}/saveCustomer.do<br />
<br />
will be mapped to the "controller" servlet.<br />
<br />
You may define any number of servlet mappings, including zero.<br />
It is also legal to define more than one mapping for the same<br />
servlet, if you wish to.<br />
--><br />
<br />
<servlet-mapping><br />
<servlet-name>controller</servlet-name><br />
<url-pattern>*.do</url-pattern><br />
</servlet-mapping><br />
<br />
<servlet-mapping><br />
<servlet-name>graph</servlet-name><br />
<url-pattern>/graph</url-pattern><br />
</servlet-mapping><br />
<br />
<br />
<!-- Define the default session timeout for your application,<br />
in minutes. From a servlet or JSP page, you can modify<br />
the timeout for a particular session dynamically by using<br />
HttpSession.getMaxInactiveInterval(). --><br />
<br />
<session-config><br />
<session-timeout>30</session-timeout> <!-- 30 minutes --><br />
</session-config><br />
<br />
<br />
</web-app><br />
<br />
<br />
<br />
</source></div>George2