17.2. Setting up DbForms

To define that the validation framework is to be used within a dbForms application, the associated XML files must be specified in the web.xml deployment descriptor (associated to the dbForms config servlet):

      <web-app>
        <!--=========== DbForms Configuration Servlet ===========--> 
        
      <servlet> 
            <servlet-name>org.dbforms.ConfigServlet</servlet-name> 
            <servlet-class>org.dbforms.ConfigServlet</servlet-class> 
    <init-param> 
                    <param-name>log4j.configuration</param-name> 
                    <param-value>log4j.properties</param-value> 
    </init-param><init-param> 
                    <param-name>resourceBundle</param-name> 
                    <param-value>ApplicationResources</param-value> 
    </init-param> 
    
      <init-param> 
                    <param-name>validation</param-name> 
                    <param-value>/WEB-INF/validation.xml</param-value> 
      </init-param> 
    
      <!--More than one validation file is possible-->
      <!--init-param>
                    <param-name>validation</param-name>
                    <param-value>/WEB-INF/validation.xml,/WEB-INF/custom/validation.xml</param-value>
      </init-param-->
      
      <init-param> 
                    <param-name>validator-rules</param-name> 
                    <param-value>/WEB-INF/validator-rules.xml</param-value> 
    
      </init-param> 
            <load-on-startup>1</load-on-startup> 
        </servlet> 
    
    

Version 1.1 of DbForms has been upgraded to use the Apache commons framework. This framework required Java XML Parser (JAXP) v1.1. Older Web containers (such as Tomcat v3.2.x) are still using JAXP v1.0 technology and are therefore incompatible.