Restrictions for Embedded GlassFish Server

The glassfish-embedded-web.jar file for embedded GlassFish Server supports only these features of nonembedded GlassFish 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 GlassFish Server JAR files, glassfish-embedded-all.jar and glassfish-embedded-static-shell.jar, support all features of nonembedded GlassFish Server with these exceptions:

• Installers

• Administration Console

• Update Tool

• Apache Felix OSGi framework

• EJB Timer Service

• The Maven plug-in for embedded GlassFish 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 GlassFish Server if a nonembedded GlassFish Server is running in parallel.

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

• default-web.xml file

• domain.xml file

• Applications directory

• Instance root directory

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

• domains

• lib

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