Hi,

JPA 2.0 will contain a Criteria API. Will hibernate implement this API ?

We are interested in this as it would allow applications to be developed without exposing a specific Persistence Layer implementation. We have a requirement that the persistence layer implementation may be changed throughout the lifetime of our project. Utilizing the JPA Criteria API would allow us to hide the hibernate implementation

DAOs do not expose the persistence layer implementation through their CRUD methods but using the hibernate Criteria API in business logic exposes hibernate (org.hibernate.Criteria etc) to the application, which we find undesirable.

Alternatively, is there another way of using the hibernate criteria API without exposing the hibernate interfaces ?

Many thanks,
Ben Dave

We'd like to do this as well. Also, will hibernate support creating a QueryBuilder instance on a client with no access to EntityManagerFactory.getQueryBuilder() or EntityManager.getQueryBuilder()?

When will this all be in Hibernate?

Hibernate 3.5 will support JPA2.0. I believe an early release is already available. It is still missing some features, but hey, it's an early release.

Check it out!

We are currently using and migrating our persistence framework over to Hibernate 3.5 betas. But what we'd like to know is, can we create a criteria query (filter) on a disconnected client (e.g. Netbeans/Eclipse RCP apps etc).

We would like to have a query builder on the client and then submit them to the server. Also, we'd like to persist these quieries, but that's another issue :)

I did read a blog from someone close to the JSR that we would be able to create disconnected criteria queries. Is this true? If so how do we do it. If not we'll stick with the current (excellent) hibernate criteria building.

Anyone know how to do this?

So can this be done yet?