engine (Sun GlassFish Enterprise Server v3 Prelude Administration Reference)

Sun GlassFish Enterprise Server v3 Prelude Administration Reference

engine

Specifies an engine for an application. 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.

Note –

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.

Superelements

application

Subelements

The following table describes subelements for the engine element.

Table 1–25 engine Subelements


Element	Required	Description
property	zero or more	Specifies a property or a variable.

Attributes

The following table describes attributes for the engine element.

Table 1–26 engine Attributes


Attribute	Default	Description
`sniffer`	none	Specifies the type of sniffer. Allowed values are as follows: `web` — Specifies that the parent application is a web application. `security` — Specifies that security is enabled for the parent application. `jpa` — Specifies that the parent application uses the Java Persistence API. `ejb` — Specifies that the parent application includes an EJB module. The EJB container add-on component must be installed in the Enterprise Server. `webservices` — Specifies that the parent application is a web service endpoint. The Metro add-on component must be installed in the Enterprise Server. `jruby` — Specifies that the parent application is a JRuby application. The JRuby add-on component must be installed in the Enterprise Server.