In some cases, you will need to provide container specific settings for your Web application. The WASCE server only includes the Tomcat Web container so only Tomcat specific settings are shown here.

The container-config element

The <container-config> element is used to hold container specific Web application settings using the following format. None of the Tomcat configuration elements are required, but if specified, they must follow the order in the example below.

where

• host is the name of a host defined in the name parameter of the initParams attribute of a virtual host <gbean> where the Web application will be deployed. See the Configuring virtual host reference for more information on configuring a virtual host.
• <cross-context/> indicates that this Web application will dispatch requests to other applications and this function should be enabled. Do not specify this tag if you want to disable cross context dispatch requests.
• <disable-cookies/> indicates that this Web application will not use cookies and this function should be disabled. Do not specify this tag if you want to enable cookies.
• valve is the name of a <gbean> that defines the first valve in a valve chain. See the valve chain reference for more information on defining valve chains.
• listener is the name of a <gbean> that defines the first listener in an lifecycle event listener chain. See the lifecycle listener reference for more information on defining lifecycle listener chains.
• realm is the name of a Tomcat realm <gbean> to be used for authentication and authorization for this Web application. If unspecified, the server will use the realm defined in the Tomcat configuration.
• manager is the name of a Tomcat manager <gbean> to be used to manage the Web application resources.
• cluster is the name of a Tomcat cluster <gbean> where the Web application will be deployed. See the Clustering and farming reference for more information on defining a Tomcat cluster.