1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 |
|
---|
3 | <!DOCTYPE web-app
|
---|
4 | PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
|
---|
5 | "http://java.sun.com/dtd/web-app_2_3.dtd">
|
---|
6 |
|
---|
7 | <!-- this is based on a sample web.xml file provided by
|
---|
8 | http://jakarta.apache.org/tomcat/tomcat-4.0-doc/appdev/web.xml.txt
|
---|
9 | -->
|
---|
10 | <web-app>
|
---|
11 |
|
---|
12 |
|
---|
13 | <!-- General description of your web application -->
|
---|
14 |
|
---|
15 | <display-name>MAT</display-name>
|
---|
16 | <description>
|
---|
17 | Metadata Analysis Tool.
|
---|
18 | </description>
|
---|
19 |
|
---|
20 |
|
---|
21 | <!-- Context initialization parameters that define shared
|
---|
22 | String constants used within your application, which
|
---|
23 | can be customized by the system administrator who is
|
---|
24 | installing your application. The values actually
|
---|
25 | assigned to these parameters can be retrieved in a
|
---|
26 | servlet or JSP page by calling:
|
---|
27 |
|
---|
28 | String value =
|
---|
29 | getServletContext().getInitParameter("name");
|
---|
30 |
|
---|
31 | where "name" matches the <param-name> element of
|
---|
32 | one of these initialization parameters.
|
---|
33 |
|
---|
34 | You can define any number of context initialization
|
---|
35 | parameters, including zero.
|
---|
36 | -->
|
---|
37 |
|
---|
38 | <context-param>
|
---|
39 | <param-name>webmaster</param-name>
|
---|
40 | <param-value>[email protected]</param-value>
|
---|
41 | <description>
|
---|
42 | The EMAIL address of the administrator to whom questions
|
---|
43 | and comments about this application should be addressed.
|
---|
44 | </description>
|
---|
45 | </context-param>
|
---|
46 |
|
---|
47 |
|
---|
48 | <!-- Servlet definitions for the servlets that make up
|
---|
49 | your web application, including initialization
|
---|
50 | parameters. With Tomcat, you can also send requests
|
---|
51 | to servlets not listed here with a request like this:
|
---|
52 |
|
---|
53 | http://localhost:8080/{context-path}/servlet/{classname}
|
---|
54 |
|
---|
55 | but this usage is not guaranteed to be portable. It also
|
---|
56 | makes relative references to images and other resources
|
---|
57 | required by your servlet more complicated, so defining
|
---|
58 | all of your servlets (and defining a mapping to them with
|
---|
59 | a servlet-mapping element) is recommended.
|
---|
60 |
|
---|
61 | Servlet initialization parameters can be retrieved in a
|
---|
62 | servlet or JSP page by calling:
|
---|
63 |
|
---|
64 | String value =
|
---|
65 | getServletConfig().getInitParameter("name");
|
---|
66 |
|
---|
67 | where "name" matches the <param-name> element of
|
---|
68 | one of these initialization parameters.
|
---|
69 |
|
---|
70 | You can define any number of servlets, including zero.
|
---|
71 | -->
|
---|
72 |
|
---|
73 |
|
---|
74 | <servlet>
|
---|
75 | <servlet-name>mat</servlet-name>
|
---|
76 | <description>mat</description>
|
---|
77 | <servlet-class>org.greenstone.mat.servlet.MatServlet</servlet-class>
|
---|
78 | </servlet>
|
---|
79 |
|
---|
80 | <servlet-mapping>
|
---|
81 | <servlet-name>mat</servlet-name>
|
---|
82 | <url-pattern>/analyse</url-pattern>
|
---|
83 | </servlet-mapping>
|
---|
84 |
|
---|
85 |
|
---|
86 | <!--
|
---|
87 | <filter>
|
---|
88 | <filter-name>UrlRewriteFilter</filter-name>
|
---|
89 | <filter-class>org.tuckey.web.filters.urlrewrite.UrlRewriteFilter</filter-class>
|
---|
90 | </filter>
|
---|
91 |
|
---|
92 | <filter-mapping>
|
---|
93 | <filter-name>UrlRewriteFilter</filter-name>
|
---|
94 | <url-pattern>/*</url-pattern>
|
---|
95 | </filter-mapping>
|
---|
96 | -->
|
---|
97 |
|
---|
98 | <!-- Define mappings that are used by the servlet container to
|
---|
99 | translate a particular request URI (context-relative) to a
|
---|
100 | particular servlet. The examples below correspond to the
|
---|
101 | servlet descriptions above. Thus, a request URI like:
|
---|
102 |
|
---|
103 | http://localhost:8080/{contextpath}/graph
|
---|
104 |
|
---|
105 | will be mapped to the "graph" servlet, while a request like:
|
---|
106 |
|
---|
107 | http://localhost:8080/{contextpath}/saveCustomer.do
|
---|
108 |
|
---|
109 | will be mapped to the "controller" servlet.
|
---|
110 |
|
---|
111 | Note: context path is determined by the servlet container -
|
---|
112 | in Tomcat, specified in server.xml -kjdon
|
---|
113 | You may define any number of servlet mappings, including zero.
|
---|
114 | It is also legal to define more than one mapping for the same
|
---|
115 | servlet, if you wish to.
|
---|
116 | -->
|
---|
117 | <!--
|
---|
118 |
|
---|
119 | <servlet-mapping>
|
---|
120 | <servlet-name>controller</servlet-name>
|
---|
121 | <url-pattern>*.do</url-pattern>
|
---|
122 | </servlet-mapping>
|
---|
123 |
|
---|
124 | <servlet-mapping>
|
---|
125 | <servlet-name>graph</servlet-name>
|
---|
126 | <url-pattern>/graph</url-pattern>
|
---|
127 | </servlet-mapping>
|
---|
128 | -->
|
---|
129 |
|
---|
130 |
|
---|
131 | <!--There is no need for this mapping, I think -->
|
---|
132 |
|
---|
133 | <!-- uncomment this if you want to use the SOAPMonitorService. You will also
|
---|
134 | need to copy the SOAPMonitorApplet*.class files from
|
---|
135 | gsdl3/comms/soap/axis/web/WEB-INF/classes to the gsdl3/web directory. See the
|
---|
136 | comms/soap/axis/docs/install.html Appendix for details about how to use this -->
|
---|
137 | <!--
|
---|
138 | <servlet-mapping>
|
---|
139 | <servlet-name>SOAPMonitorService</servlet-name>
|
---|
140 | <url-pattern>/SOAPMonitor</url-pattern>
|
---|
141 | </servlet-mapping>
|
---|
142 | -->
|
---|
143 | <!-- uncomment this if you want the admin servlet -->
|
---|
144 | <!--
|
---|
145 | <servlet-mapping>
|
---|
146 | <servlet-name>AdminServlet</servlet-name>
|
---|
147 | <url-pattern>/servlet/AdminServlet</url-pattern>
|
---|
148 | </servlet-mapping>
|
---|
149 | -->
|
---|
150 |
|
---|
151 | <!-- Define the default session timeout for your application,
|
---|
152 | in minutes. From a servlet or JSP page, you can modify
|
---|
153 | the timeout for a particular session dynamically by using
|
---|
154 | HttpSession.getMaxInactiveInterval(). -->
|
---|
155 |
|
---|
156 | <session-config>
|
---|
157 | <session-timeout>30</session-timeout> <!-- 30 minutes -->
|
---|
158 | </session-config>
|
---|
159 |
|
---|
160 | <!-- axis mime-mappings -->
|
---|
161 | <mime-mapping>
|
---|
162 | <extension>wsdl</extension>
|
---|
163 | <mime-type>text/xml</mime-type>
|
---|
164 | </mime-mapping>
|
---|
165 |
|
---|
166 | <mime-mapping>
|
---|
167 | <extension>xsd</extension>
|
---|
168 | <mime-type>text/xml</mime-type>
|
---|
169 | </mime-mapping>
|
---|
170 |
|
---|
171 | </web-app>
|
---|
172 |
|
---|
173 |
|
---|