HTTP/2 302
server: nginx
date: Sun, 03 Aug 2025 17:48:29 GMT
content-type: text/plain; charset=utf-8
content-length: 0
x-archive-redirect-reason: found capture at 20080306160709
location: https://web.archive.org/web/20080306160709/https://java.sun.com/javaee/technologies/persistence.jsp
server-timing: captures_list;dur=0.562319, exclusion.robots;dur=0.013738, exclusion.robots.policy;dur=0.005687, esindex;dur=0.012334, cdx.remote;dur=2795.856319, LoadShardBlock;dur=291.758813, PetaboxLoader3.datanode;dur=179.110844
x-app-server: wwwb-app239
x-ts: 302
x-tr: 3119
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=1
set-cookie: wb-p-SERVER=wwwb-app239; path=/
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
HTTP/2 200
server: nginx
date: Sun, 03 Aug 2025 17:48:31 GMT
content-type: text/html;charset=ISO-8859-1
x-archive-orig-server: Sun-Java-System-Web-Server-6.1
x-archive-orig-date: Thu, 06 Mar 2008 16:07:09 GMT
x-archive-orig-set-cookie: JSESSIONID=66394F09852EE7251DB38ED4044E0898;Path=/
x-archive-orig-connection: close
x-archive-guessed-content-type: text/html
x-archive-guessed-charset: iso-8859-1
memento-datetime: Thu, 06 Mar 2008 16:07:09 GMT
link:
; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate", ; rel="first memento"; datetime="Thu, 22 Mar 2007 17:07:05 GMT", ; rel="prev memento"; datetime="Thu, 28 Feb 2008 11:30:11 GMT", ; rel="memento"; datetime="Thu, 06 Mar 2008 16:07:09 GMT", ; rel="next memento"; datetime="Fri, 28 Mar 2008 08:18:43 GMT", ; rel="last memento"; datetime="Tue, 26 Nov 2024 23:35:27 GMT"
content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org
x-archive-src: 51_2_20080306113505_crawl103-c/51_2_20080306160048_crawl104.arc.gz
server-timing: captures_list;dur=1.018208, exclusion.robots;dur=0.020450, exclusion.robots.policy;dur=0.008093, esindex;dur=0.012449, cdx.remote;dur=54.000532, LoadShardBlock;dur=677.934352, PetaboxLoader3.datanode;dur=558.149344, PetaboxLoader3.resolve;dur=135.648317, load_resource;dur=158.956466
x-app-server: wwwb-app239
x-ts: 200
x-tr: 1050
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=1
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
content-encoding: gzip
Java Persistence API
Java Persistence API
Improve performance.
Java EE 5 fuels efficiency.
Java Persistence API
The Java Persistence API provides a POJO persistence model for object-relational mapping. The Java Persistence API was developed by the EJB 3.0 software expert
group as part of JSR 220, but its use is not limited to EJB software components. It can also be used directly by web applications and application clients, and
even outside the Java EE platform, for example, in Java SE applications. See JSR
220 .
Downloads
Implementation of Java Persistence API Downloads
To download a fully tested and compatible build, chose the GlassFish v1 FCS branch and download the v1 ur1 b14 binary bundle.
Articles
Using Java Persistence API Within a Visual Web Application
NetBeans IDE 6.0, the Visual Web tools, and Java Persistence API (JPA) give you greater flexibility for writing database-dependent applications.
Using the Java Persistence API on the Desktop
Learn how the Java Persistence API allows you to use POJOs in desktop applications.
The Java Persistence API: A Simpler Programming Model for Entity Persistence
See how much easier and streamlined it is to code for entity persistence with
EJB 3.0 and the Java Persistence API than with the EJB 2.1 programming model.
Tech Tips
Combining JavaServer Faces Technology, Spring, and the Java Persistence API
How to Get the Best Performance Out of a Java Persistence Implementation
Using Generics With Java Persistence
Pitfalls in Constructing Java Persistence Query Language Queries
Using Java Persistence With JavaServer Faces Technology
The Java Persistence Query Language
Using Multiple Databases in a Java Persistence Application
Inheritance and the Java Persistence API
Converting a POJO to a Persistent Entity
Resources
Java Persistence Example
This is a simple example that uses only two entities—a Customer and an
Order, with OneToMany relationships between them.
Java Persistence API FAQ
This FAQ introduces the Java Persistence API and discusses the Java Persistence
API's advantages and how it is being developed.
Tutorials
Introduction to the Java Persistence API
Persistence in the Web Tier
Persistence in the EJB Tier
The Java Persistence Query Language
Related Blogs
Sample Application Using JAX-WS, JavaServer Faces, Spring, and Java Persistence APIs on Glassfish
Sample Application Using JAX-WS, JavaServer Faces, Enterprise JavaBeans 3.0, and Java Persistence APIs on Glassfish
Sample Application Using JavaServer Faces Technology, Seam, and Java Persistence APIs on GlassFish
Using JavaServer Faces, Spring 2.0, and Java Persistence APIs in an Application
Java Persistence Query Return Types
Improving Support for Generics in the Java Persistence API
Native Query in Java Persistence Query Language
Using Relationships in the Java Persistence Query Language
Named Query in Java Persistence Query Language
More Good Examples in Java Persistence Query Language
Enumerated Annotation in GlassFish Persistence
How to Use LIKE Expression in Java Persistence Query Language
Elvis, Meet NetBeans
Using Java Persistence API in Java EE Platform - Part II
Community
GlassFish Community
Participate in the community development of the latest version of Sun Java
System Application Server, which implements the newest features in the Java EE 5
platform.
The Aquarium
Get daily news from the Glassfish Community.
Java Enterprise Community
Here's the place to exchange ideas with other developers working with Java EE technologies.
Java EE Forums
Use developer forums to share information, locate tried solutions, and learn
best practices.