iBATIS is a persistence framework which automates the mapping between SQL databases and objects in Java, .NET, and Ruby on Rails. In Java, the objects are POJOs Plain Old Java Objects. The mappings are decoupled from the application logic by packaging the SQL statements in XML configuration files. The result is a significant reduction in the amount of code that a developer needs to access a relational database using lower level APIs like JDBC and ODBC.
Other persistence frameworks such as Hibernate allow the creation of an object model in Java, say by the user, and create and maintain the relational database automatically. iBATIS takes the reverse approach: the developer starts with a SQL database and iBATIS automates the creation of the Java objects. Both approaches have advantages, and iBATIS is a good choice when the developer does not have full control over the SQL database schema. For example, an application may need to access an existing SQL database used by other software, or access a new database whose schema is not fully under the application developer's control, such as when a specialized database design team has created the schema and carefully optimized it for high performance.
On May 21, 2010 the development team forked the code creating a new project called MyBatis and making new releases there. As a consequence the Apache iBATIS project became inactive and was moved to the Apache Attic in June 2010.
For example, assume there is a database table and a Java class . To read the product record having the key into a new POJO, the following mapping is added into an iBATIS XML mapping file:
<select id="getProduct" parameterClass="java.lang.Long" resultClass="com.example.Product"> select PROD_ID as id, PROD_DESC as description from PRODUCT where PROD_ID = #value# </select>
A new Java Product object can then be retrieved from the database for product number 123 as follows:
Product resultProduct = Product sqlMapClient.queryForObject"getProduct", 123;
In the mapping file example,
#value# refers to the long integer value passed into the query. If the parameter is a Java object, then values from properties on that object can be inserted into the query using a similar
# notation. For example, if the parameter class is a
com.example.Product which has a property called
#value# can be replaced with
sqlMapClient object is an instance of class
The founder of iBATIS has publicly stated his dismay with Java 5, but has continued to release new versions of iBATIS for Java. Versions 2.3.1 and 2.3.2 came out in April 2008, and 2.3.3 in July.
The Apache iBator tool is closely related: it connects to your database and uses its metadata to generate iBATIS mapping files and Java classes.
In 2001 a project called iBATIS was started by Clinton Begin. Originally the focus was on the development of cryptographic software solutions. The first product to be released by iBATIS was Secrets, a personal data encryption and signing tool much like PGP. Secrets was written entirely in Java and was released under an open source license.
That year Microsoft published a paper to demonstrate that its recent .NET 1.0 framework was more productive than Java. For that purpose Microsoft built its own version of Sun's Web "Pet Store", a Web project that Sun had used to show Java best practices Java BluePrints. Microsoft claimed that .NET was 10 times faster and 4 times more productive than Java.
In 2002 Clinton developed an application called JPetStore to demonstrate that Java could be more productive than .NET and could also do so while achieving a better architecture than was used in the Microsoft implementation.
JPetStore 1.0 had a big impact and the database layer that Clinton used attracted the attention of the community. Soon, iBATIS Database Layer 1.0 project started, composed of two components: iBATIS DAO and iBATIS SQL Maps.
iBATIS 2.0 was released in June 2004. It was a complete redesign while keeping the same features. Clinton donated the iBATIS name and code to Apache Software Foundation and the project stayed in the ASF for six years.
Eventually iBATIS DAO was deprecated, considering that better DAO frameworks were available, such as Spring Framework.
On May 19, 2010 iBATIS 3.0 was published and simultaneously the development team decided to continue the development of the framework at Google Code. under a new project called MyBatis.
On June 16, 2010 Apache announced that iBATIS was retired and moved to the Apache Attic.