- 5.1 The magnus.conf File
- 5.2 The server.xml File
- 5.3 The obj.conf File
- 5.4 The mime.types File
- 5.5 Trust Database Files (*.db Files)
- 5.6 The server.policy File
- 5.7 The certmap.conf File
- 5.8 The default.acl File
- 5.9 The default-web.xml File
- 5.10 The login.conf File
- 5.11 The keyfile File
- 5.12 Summary
- 5.13 Self-Paced Labs
5.9 The default-web.xml File
The default-web.xml is a virtual server–specific web deployment descriptor file whose configuration settings are inherited by all web applications deployed on the virtual server. This file configures various servlets (such as the DefaultServlet and the JspServlet) and specifies the MIME types associated with specific extensions. (For more information about MIME mapping elements, see the Java Servlet specification.)
Individual web applications can override the configuration settings inherited from this file with settings contained in their own deployment descriptor file (web.xml).
The default-web.xml file is an XML-formatted file. All entries in this file are validated against the XML data type definition (DTD) for the Servlet 2.3 deployment descriptor as follows:
<!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>
Each server instance has its own default-web.xml file; therefore, there is a one-to-one correspondence between the server instance and this file.
The Administration Console and command line interface do not provide a method for managing the default-web.xml. As such, all modifications to this file must be made on a particular Administration Node. After this has been performed, the modifications must be pulled back into the configuration and then pushed out to additional Administration Nodes as appropriate.