This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
We have been around since Hibernate. So we didn't write iBATIS because we thought we could beat HIbernate. Apart from that iBATIS and Hibernate address different concerns. In a nutshell iBATIS is value based and Hibernate is concerned with object identity. The other distinction is that we are a SQL Mapping framework not a Table to Object mapping tool. We take a different approach to a similar problem.
A couple other points that I think would make iBATIS attractive to developers and companies: - iBATIS has a small learning curve. - iBATIS is SQL based and therefore those who prefer to write their SQL will feel very comfortable with it.