iBatis maps jdbc calls into hashtables (its more sophisticated than that but essentially that is what is happening) the theory being that more than a few object models being mapped through hibernate/cayenne/jdo/toplink/ojb/castor/etc/etc/etc are simply data holders and don't have any actual business logic in them anyway so they might as well be hashtables. This theory holds true fairly often but not always, thus the need for the O/R mapping frameworks.
Take a look at the ibatis front page they have a nifty graphic that shows the basics of what it does in a very concise way.
BTW: shouldn't this be on the user list instead of dev at this point?
MyFaces - myfaces.apache.org
On Mar 6, 2006, at 11:21 AM, Shashank Shanky Tiwari wrote:
I thought the whole mission of SQLMaps (an iBatis sub-project) was to map your sql query and hence the relational definition to a Java object result set. Isn't that what a O/R map is essentially trying to acheive ?
"There are only 10 types of people in the world: Those who understand binary, and those who don't."