anonymous wrote : I did some tests and they show that DAO-JDBC is better in reading data ten times.
Did you compare apples to apples? EJB3 doesn't just pull the raw data from the database, it maps the data into objects. You would have to create an object graph out of the ResultSet data you get back with your DAO in order to have a true comparison. Also, depending on your JDBC driver, JDBC may not actually pull in all the data until you iterate over the result set. The main reason to go with EJB3 is when you have a rich domain model and you want a simpler way to map object graphs into the database. It solves a complexity problem more than a performance problem. But performance can be optimized through different features that Hibernate provides (caching, join strategies, lazy loading, eager fetching, etc). You may want to learn a little more about OR mapping before you make a recommendation one way or another. I would suggest reading Hibernate in Action or taking a Hibernate course. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940525#3940525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940525 ------------------------------------------------------- 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
