Configures the web container.
The following table describes subelements for the web-container element.
Table 1–178 web-container Subelements
Element |
Required |
Description |
---|---|---|
zero or one |
Specifies session configuration information for the web container. |
|
zero or more |
Specifies a property or a variable. |
The following table describes properties for the web-container element.
Table 1–179 web-container Properties
Property |
Default |
Description |
---|---|---|
20 |
Prevents recursive include or forward statements from creating an infinite loop by setting a maximum nested dispatch level. If this level is exceeded, the following message is written to the server log: Exceeded maximum depth for nested request dispatches |
This element is deprecated. Use an application element instead.
Specifies a deployed web module.
The following table describes subelements for the web-module element.
Table 1–180 web-module Subelements
Element |
Required |
Description |
---|---|---|
zero or one |
Contains a text description of this element. |
|
zero or more |
Configures a web service endpoint. |
|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the web-module element.
Table 1–181 web-module Attributes
Attribute |
Default |
Description |
---|---|---|
none |
The name of the web module. |
|
none |
The context root at which the web module is deployed. The context root can be the empty string or just /. The context root can start with the / character, but doesn’t have to. |
|
none |
A fully qualified or relative path to the directory to which the contents of the .war file have been extracted. If relative, it is relative to the following directory: domain-dir/applications/ |
|
user |
(optional) Defines the type of the resource. For a web module, the only allowed value is user. |
|
enabled |
true |
(optional) Determines whether the web module is enabled. |
none |
(optional) Specifies an absolute or relative path to libraries specific to this module or application. A relative path is relative to domain-dir/lib/applibs. If the path is absolute, the path must be accessible to the domain administration server (DAS), which means it must be under domain-dir. To include more than one path, use a system-specific separator, such as a colon for Solaris or a semicolon for Windows. The libraries are made available to the application in the order in which they are specified. |
|
false |
(optional) Specifies whether the application has been deployed as a directory. |
Configures the grandparent web module. Applicable only if the parent engine element has a sniffer value of web.
The following table describes subelements for the web-module-config element.
Table 1–182 web-module-config Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Configures an environment entry for a web module. |
|
zero or more |
Configures a context parameter for a web module. |
This element is deprecated. Web services are implemented in the engine element.
Configures a web service endpoint, which can be a JAX-RPC/JAXWS 2.0 or JSR-109 web service.
ejb-module, j2ee-application, web-module
The following table describes subelements for the web-service-endpoint element.
Table 1–183 web-service-endpoint Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Specifies the registry where web service endpoint artifacts are published. |
|
zero or more |
Configures an eXtensible Stylesheet Language Transformation (XSLT) rule. |
The following table describes attributes for the web-service-endpoint element.
Table 1–184 web-service-endpoint Attributes
Attribute |
Default |
Description |
---|---|---|
none |
The fully qualified name of the web service. For a web service endpoint within an application, the format is as follows: module-name#endpoint-name For example: jaxrpc-simple.war#HelloIF For a web service endpoint that is a stand-alone module, the name is just the endpoint-name. |
|
OFF |
(optional) Specifies the monitoring level for this web service. For information about monitoring levels, see module-monitoring-levels. |
|
25 |
(optional) Specifies the maximum number of monitoring records stored for this endpoint. |
|
false |
(optional) Determines whether the visibility of this endpoint as a Java Business Integration service is enabled or disabled. |
Defines a work security map, which maps a principal associated with an incoming work instance to a principal in the GlassFish Server's security domain. It is possible to map multiple EIS group or user principals to the same GlassFish Server principal.
This is different from a security-map, which maps the principal received during servlet or EJB authentication to the credentials accepted by the EIS.
The following table describes subelements for the work-security-map element.
Table 1–185 work-security-map Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Maps an EIS principal to a principal defined in the GlassFish Server domain. |
|
zero or more |
Maps an EIS group to a group defined in the GlassFish Server domain. |
The following table describes attributes for the work-security-map element.
Table 1–186 work-security-map Attributes
Attribute |
Default |
Description |
---|---|---|
name |
none |
Specifies a unique name for the work security map. |
description |
none |
Specifies a text description for this element. |