jpa

Posts that have been written about Hibernate’s LazyInitializationException could probably fill whole books. Yet, I believe each of them focuses on a particular aspect of it: some on a specific solution, some on how to solve it with Spring Boot, etc. I’d like this post to be the definitive guide on the subject, even though I’m pretty sure it won’t. At least, I’ll be able to point others to it. The root cause Whether you love or hate ORM frameworks in general, they

Despite the current trend regarding &nbps;ORM frameworks, I never had any issue using JPA nor Hibernate. I must admit that my use-cases were pretty simple. Also, since that was already some years ago, we hosted those applications on our own on-site infrastructure so that the search for the ultimate performance - and its associated savings - was not a goal; empowering junior developers who were not familiar with a lot of technologies was. Interestingly enough, Hibernate actually predates JPA, so

Database access in Java went through some steps: pure Java DataBase Connectivity, proprietary frameworks, standards such as EJB Entities and Java Data Objects, OpenSource frameworks such as Hibernate and EclipseLink (known as TopLink at the time).

This is the 4th post in the Hibernate hard facts focus series. In this article, I will show the subtle differences between get() and load() methods.