Deprecation of Hibernate Criteria and how we can still prevent it

[nopalin]

@beikov

You can stick to hbm.xml if you like, it’s the same semantics as the annotation example I gave, just a different way of configuration. Like I wrote, this kind of mapping is an entity to Hibernate, regardless how you map it (XML or annotations).

No i cant, when i define hbm mapping like the example i gave before, hibernate complains with this exception:
java.lang.IllegalArgumentException: org.hibernate.hql.internal.ast.QuerySyntaxException: ConceptDto is not mapped [select generatedAlias0 from ConceptDto as generatedAlias0 where generatedAlias0.id=10]
But if i use annotations in ConceptoDto class like you suggested, it works as expected. So @Entity in a class or hbm mapping is not the same thing perhaps.

@beikov

And we don’t like to maintain 2 query APIs hence we removed the legacy Hibernate one in favor of the one forced onto use by JPA. That’s just how it is, things change. You can stick to 5.x if you like this approach that much and can’t live without it, but it sounds to me that this is not such a big issue after clearing up some misunderstandings. I understand the JPA Criteria API is sometimes cumbersome, but there are APIs out there that work on top of it that strive to provide better user experience like e.g. QueryDSL.

Well, it was really necessary to implement jpa? why dont you just continue with criteria api and ignore jpa? Maybe there is something here that we dont know which forces you to implement jpa instead of continue with criteria api. Hibernate was fabulous without jpa at first, now continue being fabulous with some headache hehe.

@beikov

I don’t know what you mean by “typed-vars” but you can use type inference in Java 11 i.e. var root = criteriaQuery.from(MyEntity.class); so you can avoid lengthy type declarations. With the JPA static metamodel (the classes ending with _ i.e. MyEntity_ ) you can even access sub-parts in a type safe manner. Not sure what the issue is there for you.

Again, is not true at all. Once i define a var somVar = ArrayList<Integer>(); and infered type is assigned i can not assign that var to another type somVar = ArrayList<String>();, so var keyword is just sugar syntax for avoiding write the original full type but has no real benefit. What i mean by typed-vars is that i have to define a lot of CriteriaQuery<Someclass> and Root<Someclass> variables inside a logic method, some times more than 10 queries for different objects, so i have a lot of vars and many times it gets confused and frustrating writing a jpa query because it is soooooo verbose and unclear. As the opposite side very good for the compiler and that’s it. I dont see the real gain writing a strong typed query for an output that will be parsed in the sql engine.

Thanks