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 abates some of 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 custom queries, or stored procedures.
iBATOR will generate:
iBATOR can run as a standalone JAR file, or as an Ant task, or as an Eclipse plugin.
iBATOR is currently under development. The legacy version (Abator) is still available. If you have suggestions for the future of iBATOR, please feel free to send them to the Java user's mailing list..
When run as an Eclipse plugin, Abator will persist the generated Java classes and SqlMap files in Eclipse projects. Abator can be run iteratively multiple time as the database design matures - and any hand coded additions to generated Java classes or SqlMap files will remain undisturbed.
Documentation for Abator is integrated into the Eclipse help system.
If you've already installed a prior version of Abator, simply run the Eclipse Install/Update tool and the new version will be found automatically.
If you've not already installed Abator, then you can use the built in Eclipse install support by following these steps:
The automatic install is much preferred, but you can also install Abator manually if you desire. To install manually, download the file AbatorForEclipse1.1.0.zip and unzip the file to some convenient location. After unzipping the update site archive, follow these steps in Eclipse: