This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I have some questions on general hibernate and JDBC.
1) Can we apply hibernate framework in application which points to database(All Tables) where having only READ access and don't have WRITE? Since hibernate objects (Session, Transaction, SessionFactory) would do some manipulation and give PO objects , will these required right access to database?.
2) Is there any situation in which we cannot apply Hibernate framework and the same conditon JDBC will workout there?
One of the primary reasons for using the Hibernate framework is to build a "persistence" component for an application. Using Hibernate for simple "Read-only" operations is overkill, when simple JDBC calls to stored procedures would work fine. However, Hibernate does include various security mechanisms at various levels to help implement a range of possible security requirements. Hibernate is an implementation of JDBC, it is not some totally different way to code database operations.