Persistence

Persistence with JPA and Hibernate is one of the main topics in my daily work and on this blog. This page provides an overview of the articles I wrote about this topic and you should expect more of them in the future.

JPA 2.1

JPA 2.1 introduced a set of new features to the specification to make the work with a relational database easier and more efficient. You can get an overview about all the new features in:

• JPA 2.1 - 12 features every developer should know.

Or if you already know what you are searching for, have a look at the list of JPA 2.1 related articles:

• Attribute Converter
• JPA 2.1 - How to implement an Attribute Converter
• JPA 2.1 Attribute Converter - The better way to persist enums
• How to use a JPA Attribute Converter to encrypt your data
• Named Entity Graph
• JPA 2.1 Entity Graph - Part 1: Named entity graphs
• Entity Graph
• JPA 2.1 Entity Graph - Part 2: Define lazy/eager loading at runtime
• Criteria API
• Criteria Update/Delete - The easy way to implement bulk operations with JPA2.1

Performance

Persisting data with Hibernate and JPA is easy, but you need to be aware of some things to avoid performance pitfalls:

• 5 ways to initialize lazy relations and when to use them
• How to activate Hibernate Statistics to analyze performance issues

Test

I usually use Arquillian to test my Java EE applications with the application server that will be used in production. Arquillian and the persistence extension can be used to manage the container, deploy the application and manage the database. I described how to do this in:

• Testing with Aliens: How to test a JPA type converter with Arquillian.