Скачать или смотреть Migrating from Criteria to CriteriaBuilder in Hibernate 5.x

Discover how to effectively migrate your Hibernate code from deprecated `Criteria` to the modern `CriteriaBuilder` approach, addressing common pitfalls and ensuring a smooth transition.
---
This video is based on the question https://stackoverflow.com/q/58221805/ asked by the user 'user1102665' ( https://stackoverflow.com/u/1102665/ ) and on the answer https://stackoverflow.com/a/74309771/ provided by the user 'Mark Burhans' ( https://stackoverflow.com/u/5248772/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Hibernate 5.x migration Criteria to CriteriaBuilder

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Migrating from Criteria to CriteriaBuilder in Hibernate 5.x

In the world of Hibernate, transitioning from legacy methods to more current practices can often present challenges. One such challenge is migrating from the deprecated Criteria API to the more robust CriteriaBuilder introduced in Hibernate 5.x. If you're trying to retrieve a unique result from your database but encounter errors rooted in this migration, you're certainly not alone. Let’s tackle this issue step by step.

Understanding the Problem: Error During Migration

When migrating your codebase, if you are using a legacy .hbm.xml file to define your entities, you may run into issues such as IllegalArgumentException while trying to add restrictions in your queries using CriteriaBuilder. The specific message — "Unable to locate Attribute with the given name" — indicates that the way attributes are accessed has changed from Hibernate 4.x to Hibernate 5.x.

Common Error Example

An example of this issue can arise in the following code block:

[[See Video to Reveal this Text or Code Snippet]]

This line of code generates an error because of how Hibernate now expects the path to be expressed.

The Solution: Correcting the Attribute Access

The solution to successfully retrieve the required attributes lies in how you're referencing nested properties. Instead of accessing nested attributes directly, you should navigate through them stepwise using the get method appropriately. Below is the correct way to rewrite the failing line:

[[See Video to Reveal this Text or Code Snippet]]

Step-by-Step Breakdown

Setup CriteriaBuilder:
Begin by creating a CriteriaBuilder instance from the session.

[[See Video to Reveal this Text or Code Snippet]]

Create CriteriaQuery:
Formulate a CriteriaQuery to specify the response type.

[[See Video to Reveal this Text or Code Snippet]]

Establish Predicate List:
Create a list to hold your restriction predicates.

[[See Video to Reveal this Text or Code Snippet]]

Add Conditions:
Depending on your conditions (e.g., checking if xyzRevision is empty), construct your predicates correctly.

[[See Video to Reveal this Text or Code Snippet]]

Complete the Query:
Finally, assemble your CriteriaQuery with the where clause and execute it.

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Migrating from Criteria to CriteriaBuilder in Hibernate 5.x is a crucial step for developers looking to bring their applications up to date. Understanding and correcting how to access attributes is fundamental to ensuring your queries run smoothly. By following the outlined steps, you can avoid common pitfalls and leverage the power of the modern Hibernate API effectively. If you encounter similar issues, remember to consult the documentation and revisit your attribute accesses for clarity.

With these adjustments, you can transition confidently into Hibernate 5.x and reap the benefits of improved functionality and performance in your applications.