Deprecation of Hibernate Criteria and how we can still prevent it

[beikov]

@nopalin

No i cant, when i define hbm mapping like the example i gave before, hibernate complains with this exception:

It complains because you didn’t define ConceptDto as entity-name in the <class/> tag.

@nopalin

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.

I don’t know what to answer here - seems you just want to argue because you don’t like the new way of doing things. Was it really necessary that you use this API? Let’s just leave it at that.

@nopalin

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.

Well, you can’t reassign a var variable, but I don’t see why this is a deal breaker. I don’t know what to tell you - if you don’t like it, don’t use it. If you want something improved, get involved in the community/spec and try to get things you think are valuable into the projects.

You can write your custom utility methods to reduce the amount of code needed for common things you think are cumbersome. Or, if you don’t want to write custom code, there are many query builder libraries (QueryDSL, Blaze-Persistence, …) that work on top of JPA which try to implement a different querying model.

If you don’t care about safety, why don’t you just concatenate strings to produce HQL and execute that HQL directly?