Hi;

I have a web application under j2ee who consults only of the data into database and post them (display).
The application do not modify the database (no operations of creation, nor of modification, nor deletion) only Reload operation.

I hesitate between Hibernate and rowset api (JDBC) ?

Which is your opinion ?

regards;

It depends, of course. Hibernate probably gives you a lot more than you need, but that doesn't mean you shouldn't use it.

We use a combination of Hibernate and JDBC (using the Spring Framework) in our app. The reason we use JDBC is because we work with some read-only data that can't be easily mapped in Hibernate. (The read-only data is in views that don't have a unique key, and we don't control the schema.) If you do use JDBC, I recommend Spring, as it has some great facilities for handling JDBC boiler-plate code. And it makes it easy to have co-existing Hibernate and JDBC Data Access Objects.

This is bad reason to use or not to use JDBC. You can use 'select distinct', you need to filter dublicates anyway, do not you ? Projection is a very usefull feature for this use case too.