I have just joined a team that is starting to build an architecture based on multiple components that will facilitate and old DBMS and a new developed DBMS. Most of the direction was towards a straight JDBC framework. But I just came form a project that utilized Hibernate. Hibernate was very powerful and fulfilled a majority of the requirements. We had created all our own integration to work with Hibernate, but really wanted to use Spring. So at my new company, I am suggesting Spring, but I am uncertain whether Hibernate or iBatis is a better solution. Hibernate is awesome in its capabilities and the limited amount of HQL that is required to produce so many of the CRUD operations. iBatis is an excellent choice as well because the framework could work with both our Java and .Net code, and utilizes SQL instead of requiring a new language to learn. Currently our database is horribly normalized...to receive improvements through a rewrite...but in the interim, both databases will need to be utilized. The team is uncertain if Hibernate would cause them to lose time in learning to adopt it, but it seems to be a very powerful solution. Any reasons why I would chose Hibernate or iBatis?

Thanks,

-jay

Hi

We have the following strategy:

1. If the DB model isn't to ugly or you are permited to change it, use Hibernate as it saves you a lot of work.
2. If even the new features of Hibernate 3 do not solve your problems fall bak to iBatis. (Actually this never happened so far ;-) ).
3. If even this fails at least use something like Springs JDBC wrappers.

IMHO the DB model is the most important thing to decide whether Hibernate is good for you, but ther are other things as well:

• http://blog.hibernate.org/cgi-bin/blosxom.cgi/Gavin%20King/batch.html
• http://www.hibernate.org/168.html

HTH
Ernst