Project

General

Profile

metacat / lib / web.xml.tomcat3 @ 2427

1
<!DOCTYPE web-app 
2
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" 
3
        "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
4

    
5
<web-app>
6

    
7

    
8
    <!-- General description of your web application -->
9

    
10
    <display-name>Metadata Catalog Demo</display-name>
11
    <description>
12
      This version is a development release only.
13
    </description>
14

    
15

    
16
    <!-- Context initialization parameters that define shared
17
         String constants used within your application, which
18
         can be customized by the system administrator who is
19
         installing your application.  The values actually
20
         assigned to these parameters can be retrieved in a
21
         servlet or JSP page by calling:
22

    
23
             String value =
24
               getServletContext().getInitParameter("name");
25

    
26
         where "name" matches the <param-name> element of
27
         one of these initialization parameters.
28

    
29
         You can define any number of context initialization
30
         parameters, including zero.
31
    -->
32

    
33
    <context-param>
34
      <param-name>jones</param-name>
35
      <param-value>jones@nceas.ucsb.edu</param-value>
36
      <description>
37
        The EMAIL address of the administrator to whom questions
38
        and comments about this application should be addressed.
39
      </description>
40
    </context-param>
41

    
42

    
43
    <!-- Servlet definitions for the servlets that make up
44
         your web application, including initialization
45
         parameters.  With Tomcat, you can also send requests
46
         to servlets not listed here with a request like this:
47

    
48
           http://localhost:8080/{context-path}/servlet/{classname}
49

    
50
         but this usage is not guaranteed to be portable.  It also
51
         makes relative references to images and other resources
52
         required by your servlet more complicated, so defining
53
         all of your servlets (and defining a mapping to them with
54
         a <servlet-mapping> element) is recommended.
55

    
56
         Servlet initialization parameters can be retrieved in a
57
         servlet or JSP page by calling:
58

    
59
             String value =
60
               getServletConfig().getInitParameter("name");
61

    
62
         where "name" matches the <param-name> element of
63
         one of these initialization parameters.
64

    
65
         You can define any number of servlets, including zero.
66
    -->
67

    
68
    <servlet>
69
      <servlet-name>metacat</servlet-name>
70
      <description>
71
        The main controlling servlet for the metacat application.
72
      </description>
73
      <servlet-class>edu.ucsb.nceas.metacat.MetaCatServlet</servlet-class>
74
      <!-- Load this servlet at server startup time -->
75
      <load-on-startup>5</load-on-startup>
76
    </servlet>
77
    
78
    <servlet>
79
      <servlet-name>HarvesterRegistration</servlet-name>
80
       <description>
81
         The replication control servlet for metacat
82
       </description>
83
      <servlet-class>edu.ucsb.nceas.metacat.harvesterClient.HarvesterRegistration</servlet-class>
84
      <load-on-startup>5</load-on-startup>
85
    </servlet>
86

    
87
    <servlet>
88
      <servlet-name>HarvesterRegistrationLogin</servlet-name>
89
       <description>
90
         The replication control servlet for metacat
91
       </description>
92
      <servlet-class>edu.ucsb.nceas.metacat.harvesterClient.HarvesterRegistrationLogin</servlet-class>
93
      <load-on-startup>5</load-on-startup>
94
    </servlet>
95

    
96
    <!--
97
    <servlet>
98
      <servlet-name>HarvesterServlet</servlet-name>
99
      <servlet-class>edu.ucsb.nceas.metacat.harvesterClient.HarvesterServlet</servlet-class>
100
      <init-param>
101
        <param-name>debug</param-name>
102
        <param-value>1</param-value>
103
      </init-param>
104
      <init-param>
105
        <param-name>listings</param-name>
106
        <param-value>true</param-value>
107
      </init-param>
108
      <load-on-startup>1</load-on-startup>
109
    </servlet>
110
    -->
111

    
112
    <servlet>
113
      <servlet-name>replication</servlet-name>
114
       <description>
115
         The replication control servlet for metacat
116
       </description>
117
      <servlet-class>edu.ucsb.nceas.metacat.MetacatReplication</servlet-class>
118
      <load-on-startup>5</load-on-startup>
119
    </servlet>
120

    
121
    <!-- Define mappings that are used by the servlet container to
122
         translate a particular request URI (context-relative) to a
123
         particular servlet.  The examples below correspond to the
124
         servlet descriptions above.  Thus, a request URI like:
125

    
126
           http://localhost:8080/{contextpath}/graph
127

    
128
         will be mapped to the "graph" servlet, while a request like:
129

    
130
           http://localhost:8080/{contextpath}/saveCustomer.do
131

    
132
         will be mapped to the "controller" servlet.
133

    
134
         You may define any number of servlet mappings, including zero.
135
         It is also legal to define more than one mapping for the same
136
         servlet, if you wish to.
137
    -->
138

    
139
    <servlet-mapping>
140
      <servlet-name>metacat</servlet-name>
141
      <url-pattern>/metacat</url-pattern>
142
    </servlet-mapping>
143

    
144
   <servlet-mapping>
145
        <servlet-name>HarvesterRegistrationLogin</servlet-name>
146
        <url-pattern>/harvesterRegistrationLogin</url-pattern>
147
    </servlet-mapping>
148

    
149
    <servlet-mapping>
150
        <servlet-name>HarvesterRegistration</servlet-name>
151
        <url-pattern>/harvesterRegistration</url-pattern>
152
    </servlet-mapping>
153
    
154
    <!-- Define the default session timeout for your application,
155
         in minutes.  From a servlet or JSP page, you can modify
156
         the timeout for a particular session dynamically by using
157
         HttpSession.getMaxInactiveInterval(). -->
158

    
159
    <session-config>
160
      <session-timeout>30</session-timeout>    <!-- 30 minutes -->
161
    </session-config>
162

    
163
</web-app>