primarily J2EE only developers who like Entity Beans and don't understand the need for this iBatis thing and its XML
Bwahahahaha!!!! How about the need for those entity bean things, their XML, their deployment descriptors, their home and remote interfaces, their DTOs, and their Business Delegate pattern so you can test the damn things.... Oh wait. Nevermind. I forgot, "the Entity Beans are my data". Yeah, and the network is the computer too. (that's the end of my completely unhelpful response) Cheers, ;-) Clinton On 7/14/06, Brandon Goodin <[EMAIL PROTECTED]> wrote:
Oh yeah, another thing... - iBATIS maps resultsets to objects unlike traditional ORM which maps tables to objects. Brandon On 7/14/06, jaybytez <[EMAIL PROTECTED]> wrote: > > I am setting up a brown bag session on Tuesday with two of the successful > apps that I have built with iBatis. I am trying to find good resources to > help me convince others in our group of the benefits of iBatis. The > developers I have to be concerned with are primarily J2EE only developers > who like Entity Beans and don't understand the need for this iBatis thing > and its XML. I on the other hand, have found the benefits of abstraction, > reduction in boilerplate code, and simplified testing. Any other items or > specific subjects I should discuss in selling iBatis to J2EE developers? > > Thanks! > > jay blanton > -- > View this message in context: http://www.nabble.com/Selling-iBatis-to-the-skeptics-tf1945597.html#a5334876 > Sent from the iBATIS - User - Java forum at Nabble.com. > >
