IMHO, there is no better. There is better for your specific case. Trying to find the best framework would only lead to a very long thread with a debate that will not lead to something useful. I for myself love hibernate, but of course some other frameworks have advantages over it.
See Chapter 4 of the Persistence in the Enterprise Book for a questionnaire to use to make the determination in your own culture and environment. Chapter 10 summarizes the evaluations we make for JDBC, iBatis, Hibernate Core, Open JPA and PureQuery in one place for easy reference.
I have also been driving IBM towards an approach called Pattern based Engineering, which is all about developing your own best practices and capturing various templates to automate the tedious, error prone parts. The reason I bring it up is that every framework is going to have some disadvantages in your specific circumstances. By using a templating engine, you can pretty easily "paper over" them until they improve. It also makes it easier to switch frameworks underneath the covers.
I hint at this in Chapter 10. For more details, check out chapter 16 of a recent IBM Redbook: