Ibator is a code generator for iBATIS. Ibator will introspect a database table (or many tables) and will generate iBATIS artifacts that can be used to access the table(s). This lessens the initial nuisance of setting up objects and configuration files to interact with database tables. Ibator seeks to make a major impact on the large percentage of database operations that are simple CRUD (Create, Retrieve, Update, Delete). You will still need to hand code SQL and objects for join queries, or stored procedures.
Ibator will generate:
There is an inheritance relationship between these classes as appropriate. Note that Ibator may be configured to generate different types of POJO hierarchies - for example, you may choose to tell Ibator to generate a single domain object for each table if you so desire.
There are different variations of these statements depending on the structure of the table (for example, if the table doesn't have a primary key, then Ibator will not generate an update by primary key function).
SqlMapClientthrough either constructor or setter injection.
Ibator is designed to run well in an iterative development environment, and Ibator can even be included as an Ant task in a continuous build environment. Important things to note when running Ibator iteratively include:
Ibator has no dependencies beyond the JRE. Ibator does require JRE 5.0 or
above. Ibator also requires that the JDBC driver implements the
DatabaseMetaData interface, especially the
"Ibator" is an iBATIS styled version of the noun abator. "Abator" means "one who abates a nuisance". This describes the purpose of Ibator - it abates some of the nuisance of creating objects and configuration files for iBATIS.
Ibator was originally named "Abator", but the name was changed as the result of a federal trade registration dispute.
Support for Ibator is provided through the iBATIS user mailing list. You may subscribe to the mailing list by sending a note to:
Once you have subscribed, you can mail questions or bug reports to:
If you want to unsubscribe from the mailing list, send a note to:
If you think you have found a bug, please ask a question about it on the user list first, before creating a JIRA issue. If you find a bug, or have a new feature request, you may open a JIRA issue for Ibator at
Please select the "Tools" component when creating any JIRA issues for Ibator.