JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1 Upgrade Guide
search filter icon
search icon

Document Information


1.  GlassFish Server Upgrade Compatibility Issues

Binary-Compatible Releases For GlassFish Server 3.1

New Default Installation Directory

Changes to Group Management Service Settings

Application Client Interoperability

Node Agent Support

HADB and hadbm Command Support

Command Line Interface: The asadmin Command

Deprecated asadmin Subcommands

Deprecated, Unsupported, and Obsolete Options

Applications That Use Java DB

Applications That Use Persistence

HTTP Service to Network Service Changes

Changes to Dotted Names

Changes to asadmin Commands

Remapping of HTTP Service Attributes and Properties

New Network Service Elements and Attributes

NSS Cryptographic Token Support

2.  Upgrading an Installation of Application Server or GlassFish Server


Applications That Use Persistence

GlassFish Server 3.1 and 3.0.1, and Sun GlassFish Enterprise Server v3 use the persistence provider EclipseLink, while earlier versions used TopLink Essentials.

An application that uses the container to create an EntityManager or EntityManagerFactory and that used Toplink Essentials as its provider will work in GlassFish Server 3.1. The container creates an EntityManager if the application uses the @PersistenceContext annotation to inject an EntityManager, as in the following example:

EntityManager em;

The container creates an EntityManagerFactory if the application uses the @PersistenceUnit annotation to inject an EntityManagerFactory, as in the following example:

EntityManagerFactory emf;

EntityManager em = emf.createEntityManager();

When the application is loaded, GlassFish Server 3.1 will translate the provider to EclipseLink and will also translate toplink.* properties in the persistence.xml to corresponding EclipseLink properties. (The actual persistence.xml file remains unchanged.)

Under certain circumstances, however, you may have to modify the persistence.xml file or your code: