Specifies a system application or a Java EE module.
An engine runs a sniffer during deployment, which is responsible for identifying a type of deployment artifact (such as a WAR file) and setting up the associated container (such as the web container). Multiple engines, each with its own sniffer, can be associated with a given application.
The application element replaces the web-module and ejb-module elements of previous releases.
For GlassFish v3 Prelude, EJB modules are not supported unless the optional EJB container add-on component is downloaded from the Update Tool. Only stateless session beans with local interfaces and entity beans that use the Java Persistence API are supported. Stateful, message-driven, and EJB 2.0 and 2.1 entity beans are not supported. Remote interfaces and remote business interfaces for any of the bean types are not supported.
Web services are not supported unless the optional Metro (JSR 109) add-on component is downloaded from the Update Tool. Without the Metro component, a servlet or EJB module cannot be a web service endpoint.
JRuby applications are not supported unless the optional JRuby add-on component is downloaded from the Update Tool.
For information about the Update Tool, see the Sun GlassFish Enterprise Server v3 Prelude Installation Guide.
system-applications, applications
The following table describes subelements for the application element.
Table 1–4 application Subelements
Element |
Required |
Description |
---|---|---|
one or more |
Configures an engine. |
|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the application element.
Table 1–5 application Attributes