Skip navigation.
Home

Apache iBATIS, the Data Mapper framework

 http://ibatis.apache.org/

 The iBATIS Data Mapper framework
makes it easier to use a database with Java and .NET applications.
iBATIS couples objects with stored procedures or SQL statements using a
XML descriptor. Simplicity is the biggest advantage of the iBATIS Data
Mapper over object relational mapping tools.

To use the iBATIS
Data Mapper, you rely on your own objects, XML, and SQL. There is
little to learn that you don't already know. With the iBATIS Data
Mapper, you have the full power of both SQL and stored procedures at
your fingertips.

iBATIS Data Mapper

The iBATIS Data Mapper provides a very
simple and flexible means of moving data between your Java and .NET
objects and a relationaldatabase. Use the full power of real SQL
without a single line of JDBC or ADO.NET code!

The Data Mapper
framework (a.k.a. SQL Maps) will help to significantly reduce the
amount of Java and .NET code that is normally neededto access a
relational database. This framework maps classes to SQL statements
using a very simple XML descriptor. Simplicity is the biggest advantage
of iBATIS over other frameworks and object relational mapping tools. To
use iBATIS you need only be familiar with your own application domain
objects (basic JavaBeans or .NET classes), XML, and SQL. There is very
little else to learn. There is no complex scheme required to join
tables or execute complex queries. Using iBATIS you have the full power
of real SQL at your fingertips. The iBATIS Data Mapper framework can
map nearly any database to any object model and is very tolerant of
legacy designs, or even bad designs. This is all achieved without
special database tables, peer objects or code generation.

 

What are the differences

What are the differences betweeb iBATES and Hibernate?


Ahmed Hashim

Software Engineer

hashimblog

re: reply

Dear Ahmad:

Ok those are answers i got from people worked with it and here's thier reply:

a) http://www.theserverside.com/news/thread.tss?thread_id=29801 

To my personal experience, iBatis 2.0 is much lighter and delivers 99%
of the features a developer looks for in a ORM framework. You can even
choose what features you want to use (dao framework, sqlmaps, caching,
lazy loading, etc.). We deployed it into production and we are very
satisfied with that.

I
compared it to Hibernate 2 (so this message might be a little
offtopic). I got puzzled when I saw that Hibernate *requires* entities
to have a key (has it been fixed in 3.0?) and does not allow (at least
this is what I understood) more mappings for the same table. From this
point of view, iBatis looks much more flexible.

 b) http://raibledesigns.com/page/rd?anchor=hibernate_vs_ibatis

c) http://www.mail-archive.com/ibatis-user-java@incubator.apache.org/msg01251.html

for me iam new to Ibatis so i searched for someone who used it.

 

 

 

Ayman Emam,
4th year, Computer Science Department,
Faculty of Computers and Information,
Cairo University, Egypt.