mirror of
https://github.com/ZSCNetSupportDept/WechatTicketSystem.git
synced 2025-10-30 01:46:18 +08:00
80 lines
2.9 KiB
XML
80 lines
2.9 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
|
|
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
|
|
version="3.1">
|
|
|
|
<!-- General description of your web application -->
|
|
|
|
<display-name>Network Support Application</display-name>
|
|
<description>
|
|
If you have any problem, please contact loli@sola.love .
|
|
</description>
|
|
|
|
<!-- 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>C3P0Test</servlet-name>
|
|
<servlet-class>love.sola.netsupport.C3P0Test</servlet-class>
|
|
</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>C3P0Test</servlet-name>
|
|
<url-pattern>/c3p0test</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 -->
|
|
</session-config>
|
|
|
|
</web-app> |