weblogic-application.xml Deployment Descriptor

 The following sections describe the weblogic-application.xml file. The weblogic-application.xml file is the BEA WebLogic Server-specific deployment descriptor extension for the application.xml deployment descriptor from Sun Microsystems. This is where you configure features such as application-scoped JDBC pools and EJB caching.

The file is located in the META-INF subdirectory of the application archive. It must begin with the following DOCTYPE declaration:

<!DOCTYPE weblogic-application PUBLIC "-//BEA Systems, Inc.//DTD WebLogic Application 8.1.0//EN"

"http://www.bea.com/servers/wls810/dtd/weblogic-application_2_0.dtd">

The following sections describe each element that can appear in the file.

weblogic-application

The weblogic-application element is the root element of the application deployment descriptor.

The following table describes the elements you can define within a weblogic-application element.

Element	Required Optional	Description
<ejb>	Optional	Contains information that is specific to the EJB modules that are part of a WebLogic application. Currently, one can use the ejb element to specify one or more application level caches that can be used by the application's entity beans. For more information on the elements you can define within the ejb element, refer to ejb.
<xml>	Optional	Contains information about parsers and entity mappings for XML processing that is specific to this application. For more information on the elements you can define within the xml element, refer to xml.
<jdbc-connection-pool>		Deprecated Zero or more. Specifies an application-scoped JDBC connection pool. For more information on the elements you can define within the jdbc-connection-pool element, refer to jdbc-connection-pool.
<security>	Optional	Specifies security information for the application. For more information on the elements you can define within the security element, refer to security.
<application-param>		Zero or more. Used to specify un-typed parameters that affect the behavior of container instances related to the application. The parameters listed here are currently supported. Also, these parameters in weblogic-application.xml can determine the default encoding to be used for requests and for responses. webapp.encoding.default—Can be set to a string representing an encoding supported by the JDK. If set, this defines the default encoding used to process servlet requests and servlet responses. This setting is ignored if webapp.encoding.usevmdefault is set to true. This value is also overridden for request streams by the input-charset element of weblogic.xml. webapp.encoding.usevmdefault—Can be set to true or false. If true, the system property file.encoding is used to define the default encoding. The following parameter is used to affect the behavior of Web applications that are contained in this application. webapp.getrealpath.accept_context_path—This is a compatibility switch that may be set to true or false. If set to true, the context path of Web applications is allowed in calls to the servlet API getRealPath. Example: <application-param> <param-name> webapp.encoding.default </param-name> <param-value>UTF8</param-value> </application-param> For more information on the elements you can define within the application-param element, refer to application-param.
<classloader-structure>	Optional	A classloader-structure element allows you to define the organization of classloaders for this application. The declaration represents a tree structure that represents the classloader hierarchy and associates specific modules with particular nodes. A module's classes are loaded by the classloader that its associated with this element. Example: <classloader-structure> <module-ref> <module-uri>ejb1.jar</module-uri> </module-ref> </classloader-structure> <classloader-structure> <module-ref> <module-uri>ejb2.jar</module-uri> </module-ref> </classloader-structure> For more information on the elements you can define within the classloader-structure element, refer to classloader-structure.
<listener>		Zero or more. Used to register user defined application lifecycle listeners. These are classes that extend the abstract base class weblogic.application.ApplicationLifecycleListener. For more information on the elements you can define within the listener element, refer to listener.
<startup>		Zero or more. Used to register user-defined startup classes. For more information on the elements you can define within the startup element, refer to startup.
<shutdown>		Zero or more. Used to register user defined shutdown classes. For more information on the elements you can define within the shutdown element, refer to shutdown.

ejb

The following table describes the elements you can define within an ejb element.

Element	Required Optional	Description
<entity-cache>		Zero or more. The entity-cache element is used to define a named application level cache that is used to cache entity EJB instances at runtime. Individual entity beans refer to the application-level cache that they must use, referring to the cache name. There is no restriction on the number of different entity beans that may reference an individual cache. Application-level caching is used by default whenever an entity bean