Restrictions for Embedded Enterprise Server

The glassfish-embedded-web.jar file for embedded Enterprise Server supports only these features of nonembedded Enterprise Server:

• The following web technologies of the Java EE platform:

  • Java Servlet API 2.5

  • JavaServer Pages^TM (JSP^TM) technology 2.1

  • JavaServer^TM Faces technology 1.0

• JDBC-technology connection pooling

• Java Persistence API 1.0

• Java Transaction API

• Java Transaction Service

The other embedded Enterprise Server JAR files, glassfish-embedded-all.jar and glassfish-embedded-static-shell.jar, support all features of nonembedded Enterprise Server with these exceptions:

• Installers

• Administration Console

• Update Tool

• Apache Felix OSGi framework

• EJB Timer Service

• The Maven plug-in for embedded Enterprise Server does not support application clients.

• Applications that require ports for communication, such as remote EJB components, do not work with the EJB 3.1 Embeddable API running with embedded Enterprise Server if a nonembedded Enterprise Server is running in parallel.

Embedded Enterprise Server requires no installation or configuration. As a result, the following files and directories are absent from the file system until embedded Enterprise Server is started:

• default-web.xml file

• domain.xml file

• Applications directory

• Instance root directory

When embedded Enterprise Server is started, the base installation directory that Enterprise Server uses depends on the options with which Enterprise Server is started. For more information, see Specifying an Embedded Enterprise Server File System. If necessary, embedded Enterprise Server creates a base installation directory. Embedded Enterprise Server then copies the following directories and their contents from the Java archive (JAR) file in which embedded Enterprise Server is distributed:

• domains

• lib

If necessary, Enterprise Server also creates an instance root directory.