iBATIS has a few goals and philosophies that you will find it adhering to:
- iBATIS does it's best to maintain the 80/20 rule. iBATIS seeks to make 80% of what you would do with JDBC easier while realizing there will be things that are better handled by straight JDBC.
- iBATIS has a small learning curve.
- iBATIS retains the power of straight forward unparsed unabashed unfettered 100% pure vine ripened SQL
- iBATIS is value based. We do not attempt to retain object identity within a session or cache. If two "Person" objects exist with the same internal values, they will remain to distinct objects. This is in contrast to ORM frameworks which strive to maintain object identity.
- iBATIS does not give deference to the Object or Relational side. We work hard to provide equal oppotunity to developers to decide for themselves if deference should be given to the object side or the relational side.
If i can think of anything else i'll let you know :)
Brandon Goodin
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.
