iBATIS will always be different for one simple reason: iBATIS is not an ORM.
As you've said, EJB3 is basically a specification designed by a
committee including Hibernate, Toplink and other vendors. All the
reasons you've chosen to use iBATIS will stand true when you compare
against EJB3, Hib
Hello all, friends, I'm working on my projects with iBatis two years ago more or less, and I found that iBatis was the best way to map my SQL's to Objects. Now we have a new persistence standar, EJB3, that promises that persistence will be very easy to implement in our new projects. EJB3 is quite s
