The explanations provided in http://www.hibernate.org/15.html and http://www.hibernate.org/157.html I find very comprehensive and substantial.
The issues related to performance have always been very easy to be misunderstood and wrongly interpreted... I just want to mention that using DAO & JDBC forces you to work on a lower level, which means that you are less likely to do unnecessary things. When using additional layer (even the best ORM) it is often much easier to do "wrong" things that slow down the performance (like unnecessary eager collections & objects). But it does not mean that the problem is in the ORM itself. As a matter of fact, I am not too proficient in hibernate, but I think that it is pretty good at what it does. So, I'd almost always prefer hibernate3/EJB3 (with annotations) to JDBC/DAO, because I find that these technologies have more pros than cons. As a comparison, I'll mention that I'd almost never prefer EJB2 persistence to JDBC/DAO... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942979#3942979 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942979 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
