Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

What's new in JPA 2.0?

DZone's Guide to

What's new in JPA 2.0?

· Java Zone
Free Resource

Learn how our document data model can map directly to how you program your app, and native database features like secondary indexes, geospatial and text search give you full access to your data. Brought to you in partnership with MongoDB.

Wouldn't you like to know?  Check out this week's refcard for a look at the big changes in JPA 2.0.

Overview

Written for developers experienced with JPA 1.0 who are interested in learning about JPA 2.0, this DZone Refcard covers the primary new features introduced in the JPA 2.0 release and provides explanations for how they can be used. Some of the topics covered include Mappings, Shared Cache, and Validation.


About the Author

Mike Keith has been a distributed systems and persistence expert for over 20 years. He co-led the expert group that produced the first release of JPA and co-authored the premier JPA reference book, Pro EJB: Java Persistence API, followed up with Pro JPA 2: Mastering the Java Persistence API. He works at Oracle as an architect for enterprise Java and represents Oracle on numerous expert groups and specifications, including the Java EE platform specification, JPA, and others. He leads the Gemini Enterprise Modules project at Eclipse, and is a member of the Eclipse Runtime project PMC.

Discover when your data grows or your application performance demands increase, MongoDB Atlas allows you to scale out your deployment with an automated sharding process that ensures zero application downtime. Brought to you in partnership with MongoDB.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}