0

Preparing a proposal for my team, I have the obvious ones.

Ibatis is retired, no more fixes/enhancements. Hibernate is the de-factor standard. Hibernate has more/better documentation.

What would add or take away from the proposal?

Thanks

Andy
  • 8,593
  • 7
  • 42
  • 66
  • 2
    I think your facts might be out of date ibatis has been reborn as mybatis: http://www.mybatis.org/ – mikerobi Oct 25 '10 at 00:22
  • thanks..i was not aware. – Andy Oct 25 '10 at 01:04
  • 1
    There are just too many dupes: http://stackoverflow.com/questions/1984548/hibernate-vs-ibatis, http://stackoverflow.com/questions/3762643/hibernate-vs-ibatis, http://stackoverflow.com/questions/716532/hibernate-ibatis-jee-or-other-java-orm-tool, http://stackoverflow.com/questions/1747413/hibernate-or-ibatis-or-something-else – Pascal Thivent Oct 25 '10 at 01:33

1 Answers1

0

Hibernate is dynamic, generated SQL. If it works for you, great. Some people don't like the SQL they get from Hibernate. iBatis gives you control over the SQL that's used.

Hibernate makes no sense if you don't have a good object model.

I'm not sure I agree that Hibernate is a de-facto standard.

How much more documentation do you need? Is the iBatis documentation sufficient?

Some problems are "done". Maybe iBatis is complete. What features do you think are needed to be added?

duffymo
  • 293,097
  • 41
  • 348
  • 541