For a very simple and straightforward CRUD application, I would probably use Grails. Can't beat the (initial) productivity of that.
Other than that, it really depends on what you want to do. I found that Hibernate works very well for rapid prototyping. Just create a class and a simple mapping file (use the default values wherever possible), let it generate the DB schema and you're good to go, no need to write any SQL. The initial effort with iBATIS is a bit higher IME, but once you have it running, there aren't any surprises. With Hibernate, I've made the experience that you might find problems late on and have to fine tune a lot. YMMV ... If you have to use a legacy DB schema that you can't change, I would use iBATIS, as there are some scenarios that Hibernate will not be easy to use in. Nils On Fri, 06 Jul 2007 11:35:26 +1000, "Zoran Avtarovski" <[EMAIL PROTECTED]> said: > This being an iBatis list I dare say you will get overwhelming support > for > it (which I agree with). > > There are a lots of "independent" comparisons out there. Try googling > ibatis > v. Hibernate. You will see that each has its advantages and disadvantages > with relation to the type of project you are doing and the skill set of > your > team. > > Z. > > -- ================================== [EMAIL PROTECTED]
