... Instance documents may indicate the published version of the schema using the xsi:schemaLocation attribute for the Java EE namespace with the following location: http://www.jboss.org/j2ee/schema/jboss-web_7_0.xsd ]]> The following conventions apply to all Java EE deployment descriptor elements unless indicated otherwise. - In elements that specify a pathname to a file within the same JAR file, relative filenames (i.e., those not starting with "/") are considered relative to the root of the JAR file's namespace. Absolute filenames (i.e., those starting with "/") also specify names in the root of the JAR file's namespace. In general, relative names are preferred. The exception is .war files where absolute names are preferred for consistency with the Servlet API. This is the root element of jboss-web deployment descriptor. The jboss-web element is the root element of jboss-web.xml file. It contains all the information used by jboss but not described in the web.xml file. All of it is optional. Defines a web container listener. The module element allows specifying from which module in the application server the specified class will be loaded. The listener type element defines which events the listener will recieve from the web container. LIFECYCLE ]]> Defines a web container valve. The module element allows specifying from which module in the application server the specified class will be loaded. A container valve is used to intercept the request that will be processed by the servlet. It is invoked as part of a chain, before the invocation of the webapp's filter chain. The overlay element specifies additional static files overlays for this web application. The content of the element should be a folder in the filesystem containing the static files that will overlay the webapp's static files, similar to what happens with regular JAR overlays. The disable-cross-context element specifies if cross context access should be enabled for this webapp, allowing it to use the request dispatcher to access other webapps deployed in the application server. The use-jboss-authorization element specifies if the JBoss authorization layer should be used. The disable-audit element specifies if the security audit logging should be disabled. The distinct-name element specifies the EJB 3 distinct name for this web application. The jacc-star-role-allow element specifies whether the jacc permission generating agent in the web layer needs to generate a WebResourcePermission(url,null) permission such that the jacc provider can make a decision as to bypass authorization or not. The context-root element specifies the context root of a web application. This is normally specified at the ear level using the standard JEE application.xml descriptor, but it may be given here for standalone wars. This should not override the application.xml level specification. www.jboss-store.org ]]> SET_AND_GET or SET_AND_NON_PRIMITIVE_GET or SET ]]> SESSION or ATTRIBUTE ]]> SYNCHRONOUS or ASYNCHRONOUS ]]> 0 : Session will be replicated to *all* nodes (i.e. total replication) 0 : Session will not be replicated (i.e. local mode) < 0 : Session will be replicated only to the specified number of nodes (i.e. distribution mode) Default value, if not explicitly set, is taken from the distributed cache configuration. By default, this is -1, i.e. total replication. ]]> ... Default value if not explicitly set is the overall web container default as set in the deployers/jbossweb.deployer service. By default that is set to "false". ]]> SESSION, the session's attribute map is replicated along with the metadata, so it can be fairly costly. With other granularities, the metadata object is replicated separately from the attributes and only contains a String, and a few longs, ints and booleans. A value of 0 means the metadata will be replicated whenever the session is accessed. A value of -1 means the metadata will be replicated only if some other activity during the request (e.g. modifying an attribute) has resulted in other replication work involving the session. A positive value greater than the HttpSession.getMaxInactiveInterval() value will be treated as a likely misconfiguration and converted to 0; i.e. replicate the metadata on every request. ]]> The run-as-principal element specifies whether a specific run-as identity is to be used. If there is a run-as role defined for a servlet, there can also be a run-as-principal defined here. If you don't define a run-as principal the callee will see ctx.getUserPrincipal() == 'anonymous' 30 (seconds) ]]> 300 (seconds) ]]> true or false (default value) ]]>