Re: Re: increase event pool size

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>

    <display-name>jExam Web application V3</display-name>
    <description>
      No description at this time. Will be later added.
    </description>
	 
	 <context-param>
      <param-name>webmaster</param-name>
      <param-value>[email protected]</param-value>
      <description>
        The EMAIL address of the administrator to whom questions
        and comments about this application should be addressed.
      </description>
    </context-param>

    <!-- ============================================================== -->
    <!--              Begin Log4j context parameters                    -->
    <!-- ============================================================== -->
    <context-param>
        <!-- preferred repository selector. "preferred" because if one
             is already installed, this choice is ignored. -->
        <param-name>log4j-selector</param-name>
        <param-value>org.apache.log4j.selector.ContextJNDISelector</param-value>
    </context-param>
    <context-param>
        <!-- relative path to config file within current webapp -->
        <param-name>log4j-config</param-name>
        <param-value>WEB-INF/log4j.xml</param-value>
    </context-param>
    <context-param>
        <!-- config file re-reading specified in milliseconds...
             Note that if the webapp is served directly from a
             .war file, configureAndWatch() cannot be used because
             it requires a system file path. In that case, this
             param will be ignored.  Set to 0 or don't specify this
             param to do a normal configure(). -->
        <param-name>log4j-cron</param-name>
        <param-value>5000</param-value>
    </context-param>
    <!-- Below are optional context params for use with a File Appender.
         "log4j-log-home" specifies a path to be read from a log4j xml
         config file as a system property. The system property name is
         dynamically generated, by default, and takes on the following pattern:
             [context path].log.home
         If the app has a context path of "/Barracuda", the system
         variable name would be "Barracuda.log.home".  So,
         the FileAppender in log4j.xml would contain a param which looks like:
             <param name="File" value="${Barracuda.log.home}/arbitraryLogFileName.log" />
         Dynamic generation of a predictable system property name has only been tested
         successfully on Tomcat and may not work in other containers. As such,
         one may specify the desired system property name using the
         "log4j-sysprop-name". If specified, this name will be used
         in place of the dynamically generated system property name.  It is
         recommended that naming pattern match that described above.
         If the "log4j-log-home" context param is not specified, the
         path associated with the generated system variable defaults to
         the WEB-INF/logs directory of the current webapp which is created
         if it doesn't exist... unless the webapp is running directly
         from a .war file.  In the latter case, this context param
         *must* be specified if using a FileAppender.
         Note that, if specified, the value is treated as an absolute
         system path which is not relative to the webapp. -->
    <!-- <context-param>
        <param-name>log4j-log-home</param-name>
        <param-value>/usr/local/logs/tomcat</param-value>
    </context-param> -->
    <!-- <context-param>
        <param-name>log4j-sysprop-name</param-name>
        <param-value>Barracuda.log.home</param-value>
    </context-param> -->
    <!-- ============================================================== -->
    <!--              End Log4j context parameters                      -->
    <!-- ============================================================== -->

    <!-- ============================================================== -->
    <!--     Listeners - Note: Optional. May be commented out for those -->
    <!--                 limited to Servlet-2.2 compliant engines       -->
    <!-- ============================================================== -->
    <listener>
        <listener-class>
        de.jexam.web.servlet.WebUserSessionLoginManager
        </listener-class>
    </listener>
    <!-- Shuts down all loggers and appenders at webapp shutdown -->
    <listener>
        <listener-class>
        org.apache.log4j.servlet.InitContextListener
        </listener-class>
    </listener>

    <!-- ============================================================== -->
    <!--                ObjectRepositoryAssembler declarations          -->
    <!-- ============================================================== -->
    <!-- GlobalRepository Setup -->
    <servlet>
        <servlet-name>GlobalRepositoryAssembler</servlet-name>
        <servlet-class>org.enhydra.barracuda.plankton.data.ObjectRepositoryAssembler</servlet-class>
        <init-param>
            <param-name>AssemblyDescriptor</param-name>
            <param-value>WEB-INF/object-repository.xml</param-value>
        </init-param>
        <init-param>
            <param-name>LogHeartbeat</param-name>
            <param-value>true</param-value>
        </init-param>
        <load-on-startup>2</load-on-startup>
    </servlet>


    <!-- ============================================================== -->
    <!--                Baracuda declarations                           -->
    <!-- ============================================================== -->
    <!-- If you are going to use the event model, you must specify the  -->
    <!-- ApplicationGateway                                             -->
    <servlet>
        <servlet-name>ApplicationGateway</servlet-name>
        <servlet-class>org.enhydra.barracuda.core.event.ApplicationGateway</servlet-class>
        <init-param>
            <param-name>ApplicationAssembler</param-name>
            <param-value>org.enhydra.barracuda.core.event.DefaultApplicationAssembler</param-value>
        </init-param>
        <init-param>
            <param-name>AssemblyDescriptor</param-name>
            <param-value>/WEB-INF/event-gateway.xml</param-value>
        </init-param>
        <init-param>
            <param-name>SAXParser</param-name>
            <param-value>org.apache.xerces.parsers.SAXParser</param-value>
        </init-param>
        <load-on-startup>3</load-on-startup>
    </servlet>

    <!-- If you are going to use BAction components on HTML Forms,      -->
    <!-- you must specify the FormGateway                               -->
    <servlet>
        <servlet-name>FormGateway</servlet-name>
        <servlet-class>org.enhydra.barracuda.core.comp.helper.FormGateway</servlet-class>
    </servlet>

    <!-- If you want to support disabling the back button on HTML Forms -->
    <!-- you must specify the ParamGateway                              -->
    <!--servlet>
        <servlet-name>ParamGateway</servlet-name>
        <servlet-class>org.enhydra.barracuda.core.helper.servlet.ParamGateway</servlet-class>
    </servlet-->

    <!-- ============================================================== -->
    <!--                Custom declarations                             -->
    <!-- ============================================================== -->


    <!-- ============================================================== -->
    <!--                Baracuda mappings                               -->
    <!-- ============================================================== -->
    <!-- This is needed for the ApplicationGateway                      -->
    <servlet-mapping>
        <servlet-name>ApplicationGateway</servlet-name>
        <url-pattern>*.event</url-pattern>
    </servlet-mapping>

    <!-- This is needed for the FormGateway                             -->
    <servlet-mapping>
        <servlet-name>FormGateway</servlet-name>
        <url-pattern>*.form_forward</url-pattern>
    </servlet-mapping>

    <!-- This is needed for the ParamGateway                            -->
    <!--servlet-mapping>
        <servlet-name>ParamGateway</servlet-name>
        <url-pattern>*.param_map</url-pattern>
    </servlet-mapping-->

    <!-- ============================================================== -->
    <!--                Custom mappings                                 -->
    <!-- ============================================================== -->


    <!-- 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>15</session-timeout><!-- 15 minutes -->
    </session-config>

    <security-role>
      <description>jExam V3 security role for web application</description>
      <role-name>web</role-name>
    </security-role>

    <env-entry>
      <description>JNDI logging context for this webapp</description>
      <env-entry-name>log4j/logging-context</env-entry-name>
      <env-entry-value>BarracudaMVC</env-entry-value>
      <env-entry-type>java.lang.String</env-entry-type>
    </env-entry>
 
    <error-page>
      <error-code>404</error-code>
      <location>/404.shtml</location>
    </error-page>
    <error-page>
      <error-code>500</error-code>
      <location>/500.shtml</location>
    </error-page>

    <resource-ref>
	 	<description>The NIS authentication service</description>
      <res-ref-name>jexam/NISAuthenticationService</res-ref-name>
      <res-type>de.jexam.server.jboss.service.nis.NISAuthenticator</res-type>
      <res-auth>Container</res-auth>
    </resource-ref>

</web-app>