Frames No Frames

Running Abator

Abator can be run in the following ways:

• From the command line with an XML configuration
• As an Ant task with an XML configuration
• From another Java program with an XML configuration
• From another Java program with a Java based configuration

Each method is described in detail below.

Note: there is also an Eclipse plugin for Abator that adds extra function - namely good integration into Eclipse, an Eclipse enabled Ant task, and support for automatic merging of Java files. See the Abator home page for information on installing the Eclipse plugin.

Important: When running outside of an IDE environment like Eclipse, Abator interprets the targetProject and targetPackage attributes in all XML configurations as follows:

• targetProject is assumed to be an existing directory structure. Abator will fail if this directory structure does not exist.
• targetPackage will be translated to a suitable subdirectory structure of the targetProject directory structure. Abator will create these subdirectories if necessary.

Running Abator from the Command Line

Abator may be run directly from the command line. The JAR manifest includes the name of the default class (org.apache.ibatis.abator.api.AbatorRunner) or you may specify it yourself. The AbatorRunner class accepts several arguments as detailed below:

You must create an Abator XML configuration file to run Abator from the command line. If the file is named "abatorConfig.xml", then any of the following command lines will run Abator:

   java -jar abator.jar -configfile abatorConfig.xml
   java -jar abator.jar -configfile abatorConfig.xml -overwrite
   java -cp abator.jar org.apache.ibatis.abator.api.AbatorRunner -configfile abatorConfig.xml
   java -cp abator.jar org.apache.ibatis.abator.api.AbatorRunner -configfile abatorConfig.xml -overwrite

Running Abator from Ant

Abator includes a simple Ant task. The task must be defined in your build.xml file, and the task has three parameters. Here is an example build.xml file:

   <project default="genfiles" basedir=".">
     <property name="generated.source.dir" value="${basedir}" />

     <target name="genfiles" description="Generate the files">
       <taskdef name="abator"
                classname="org.apache.ibatis.abator.ant.AbatorAntTask"
                classpath="abator.jar" />
       <abator overwrite="true" configfile="abatorConfig.xml" verbose="false" >
         <propertyset>
           <propertyref name="generated.source.dir"/>
         </propertyset>
       </abator>
     </target>
   </project>

Abator task attributes are as follows:

Notes:

• The classpath on the <taskdef> is used to tell Ant where the Abator JAR file is. This is optional if you add Abator to the Ant classpath in one of the other ways described in the Ant manual
• The name of the task can be anything you desire, "abator" is simply an example
• The task supports an optional nested <propertyset> element which is the standard Ant property set type. This can be used to pass parameters into a configuration file. For example, the above property generated.source.dir can be accessed in the Abator configuration file with the escape sequence ${generated.source.dir}
• If a property is specified in the configuration file and is not resolved, then the escaped property string will be passed "as is" into the generated code.

Running Abator from Java with an XML Configuration File

The following code sample shows how to call Abator from Java. It does not show exception handling, but that should be obvious from the compiler errors :)

   List warnings = new ArrayList();  // Abator will add Strings to this list
   boolean overwrite = true;
   File configFile = new File("abatorConfig.xml");
   AbatorConfigurationParser cp = new AbatorConfigurationParser(warnings);
   AbatorConfiguration config = cp.parseAbatorConfiguration(configFile);
   DefaultShellCallback callback = new DefaultShellCallback(overwrite);
   Abator abator = new Abator(config, callback, warnings);
   abator.generate(null);

Notes:

• Configuration file properties may be passed to the parser as a parameter on the AbatorConfigurationParser constructor. If not passed explicitly, the JVM system properties will be searched for the value of configuration file properties. For example, the property generated.source.dir can be accessed in the Abator configuration file with the escape sequence ${generated.source.dir}
• If a property is specified in the configuration file and is not resolved, then the escaped property string will be passed "as is" into the generated code.

Running Abator from Java with a Java Based Configuration

The following code sample shows how to call Abator from Java only. It does not show exception handling, but that should be obvious from the compiler errors :)

   List warnings = new ArrayList();  // Abator will add Strings to this list
   boolean overwrite = true;
   AbatorConfiguration config = new AbatorConfiguration();

   //   ... fill out the config object as appropriate...

   DefaultShellCallback callback = new DefaultShellCallback(overwrite);
   Abator abator = new Abator(config, callback, warnings);
   abator.generate(null);