Web.xml Deployment Descriptor

Web.xml is a deployment descriptor of a web application. It is the standard file where Valuemation web server-related parameters are stored.

The file resides in the <Valuemation .war archive>\WEB-INF folder.
Each parameter entry in the file consists of parameter name, default value and a description or comment.

The 'web.xml' file is part of the application WAR file. This means that to deploy changes made in the web.xml file, a new war file must be created.

Note: The same settings can also be made using 'vmconfig.properties' or JNDI resources. Please see also the 'vmconfig.properties' topic.

The XML parameter structure follows this pattern:

<init-param>
A tag delimiting a parameter. The single <init-param> tag is used for each parameter.
<param-name>
This tag specifies the name of the parameter within an <init-param> element.
<param-value>
This tag specifies the value of the parameter within an <init-param> element.
<description>
A description of the parameter.

Example: A parameter which enables ARIA tags.

<init-param>
    <param-name>addARIATags</param-name>
    <param-value>false</param-value>
    <description>
      When set to 'true' the ARIA tags are added to DOM elementes. No other functional or change is doe (in contrary to ScreenReader mode).
      The ARIA tags can be also used to define more proper element locators used by web testing frameworks like e.g. SilkTest.
          Default: false
   </description>
</init-param>

An inherent part of the 'web.xml' deployment descriptor is a definition of servlets. The most important one is the 'vmweb' servlet (Valuemation) with its parameters. The rest of the 'web.xml' is formed by other servlets ('vmsf', 'peconsole'...), and filters ('CORS', 'ResponseHeaderFilter'...).

The most important servlets and filters are:

In This Chapter

Filter: 'ResponseHeaderFilter'

Filter: 'CORS'

Filter: 'SecurityFilter'

Filter: 'RequestLoggingFilter'