Hibernate for stored procedure access

Question

We have business restriction in accessing the database only through stored procedure calls. Caching is also not allowed. Is there value in using Hibernate framework where in you are not using the features like building object relationship based complex queries or caching? We are using considering using the lightweight jdbc option.

Answer 1

Hibernate makes sense if you're going to map objects to tables. I don't see how HQL can benefit you otherwise.

I would look into JDBC or Spring JDBC instead.

Answer 2

Hibernate's lazy loading and entity mapping still brings a lot of value to the table. I would go for it.