Metacat

<!DOCTYPE web-app

    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"

        "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">

<web-app>

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

    <display-name>Metadata Catalog Demo</display-name>

    <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 number of context initialization

         parameters, including zero.

    -->

    <context-param>

      <param-value>jones@nceas.ucsb.edu</param-value>

        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>metacat</servlet-name>

      <description>

        The main controlling servlet for the metacat application.

      </description>

      <servlet-class>edu.ucsb.nceas.metacat.MetaCatServlet</servlet-class>

      <!-- Load this servlet at server startup time -->

      <load-on-startup>5</load-on-startup>

    </servlet>

      <servlet-name>marine</servlet-name>

       <description>

         The marine incarnation of metacatServlet

       </description>

      <servlet-class>edu.ucsb.nceas.metacat.marine.marineServlet</servlet-class>

      <load-on-startup>5</load-on-startup>

    </servlet>

         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>metacat</servlet-name>

      <url-pattern>/metacat*</url-pattern>

    </servlet-mapping>

    <servlet-mapping>

      <servlet-name>marine</servlet-name>

      <url-pattern>/marineServ*</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>