Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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
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?