This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
No, iBATIS does not generate your schema for you (unless Abator does it, which you can look into).
But honestly, if I were in a situation where I was able to build my own database schema from scratch, I'd probably use Hibernate anyway.
iBATIS was built for what I call "red pill" projects -- or real projects. ;-)
I work mostly on "enterprise" systems I've never had the luxury of having full control over the database design, let alone the luxury to generate the schema. In almost all cases the database already exists and in most cases it's not even a single database.
So yes, if you're generating the schema, use Hibernate. If you ever run into an existing enterprise or legacy system, use iBATIS. That said, I do know a lot of people who choose iBATIS even when they are starting from scratch.
Make your own schema's and have as much fine tuned, intricate queries as you like. Go wild! iBatis will map the result-set to your objects with lightning speed... as long as you have defined the mapping correctly!
also there is abator [ December 05, 2006: Message edited by: Salman Khattak ]
SCJP Java 1.4 - 06/2003<br />Power corrupts and absolute power corrupts absolutely!
That said, I do know a lot of people who choose iBATIS even when they are starting from scratch.
I never like the idea of generating the DB schema. DB design, to me, is far too important for it to be generated. Even if I start from stratch, I like to design & normalise the DB 1st (and not the OO design). As such, I think iBatis is more suitable for me than the OO-centric Hibernate.