WAS persistence providers
Persistence providers are implementations of the Java Persistence API (JPA) specification and can be deployed in the Java EE compliant application server that supports JPA persistence.
The EJB 3.0 and later specifications require an application server container that supports the EJB 3.0 and later programming model must provide a JPA implementation. This is also referred to as a persistence provider.
The following persistence providers come bundled with the product:
- EclipseLink: This is the default Java Persistence API (JPA) 2.1 specification provider.
- WSJPA: This is the default Java Persistence API (JPA) 2.0 specification provider and an extension of the Apache OpenJPA provider implementation.
- Apache OpenJPA: This is an optional persistence provider that supports the Java Persistence API (JPA) 2.0 specification.
If an explicit provider element is not specified in the persistence unit definitions, the application server will use the default persistence provider, relative to the required JPA specification.
Tasks
- Configure a default persistence provider
Use a default persistence provider, or specify a persistence provider for the application. With the application server's JPA persistence provider, we can take advantage of the stability and application extensions provided with the application server's implementation of JPA. We can decide which persistence implementation best fits our needs. If an application relies on a specific persistence provider for certain functions and settings, we should specify the provider in the persistence unit definition to avoid any incompatibilities.
- Use third-party persistence providers
Use third-party persistence providers in the application server environment.
Subtopics
Related:
Java Persistence API (JPA) architecture Use third-party persistence providers IBM Optim pureQuery Runtime