/*

  * Copyright 2006 Outsource Cafe, Inc.

  *

  * Licensed under the Apache License, Version 2.0 (the 'License')

  * you may not use this file except in compliance with the License.

  * You may obtain a copy of the License at

  *

  *    http://www.apache.org/licenses/LICENSE-2.0

  *

  * Unless required by applicable law or agreed to in writing, software

  * distributed under the License is distributed on an 'AS IS' BASIS,

  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

  * See the License for the specific language governing permissions and

  * limitations under the License.

  */

 package org.javagen.revgen;

 import org.javagen.agile.core.ioc.spring.SpringMain;

 /**

  * Loads RevGen configuration and executes code generation pipeline using Spring framework IoC BeanFactory.

  * <p>

  * This class excepts two arguments: <code>revgen.properties</code> and <code>RevGenSpringConfig.xml</code>.

  * <p>

  * <code>revgen.properties</code> is meant to be the first (ie easiest) level of RevGen configuration specifying:

  * <ul>

  * <li>Database connection properties</li>

  * <li>Generated project name and directory location</li>

  * <li>Source folder layout</li>

  * <li>Output types: annotations vs XML, Hibernate vs Spring vs EJB3 implementations, etc.</li>

  * <li>The global overwrite policy (aka <code>overwriteAll</code>)</li>

  * </ul>

  * 

  * Any type of configuration can be achieved using <code>RevGenSpringConfig.xml</code> including:

  * <ul>

  * <li>Pipeline components and order of execution</li>

  * <li>Template names, locations and types and their artifact naming patterns and relative output locations</li>

  * <li>Per-template overwrite predicates</li>

  * <li>Binding templates to model instances</li>

  * <li>Root structure of model tree including global properties and parent containers for generated model instances</li>

  * <li>Default and artifact-specific naming patterns using model and emitter contexts</li>

  * <li>Reading, writing and merging of metadata</li>

  * <li>Database table selection</li>

  * <li>Code naming and conversion implementations</li>

  * <li>Anything that <code>revgen.properties</code> can specify</li>

  * </ul>

  * <p>

  * <p>

  * Properties inputs have the following precedence from lowest to highest:

  * <ol>

  * <li>Properties specified in the <code>GlobalPropertyHolder</code> bean within the RevGenSpringConfig.xml file.</li>

  * <li>Properties specified in the external <code>propertyFile</code>. Note: this can be specified as a <code>GlobalPropertyHolder</code> property and overridden here.</li>

  * <li>Properties specified in the <code>properties</code> instance.  Note: these are usually set by the invoking tool (i.e. Maven).</li>

  * </ol>

  * This is an extremely flexible way to configure the code generator, avoiding a one-size-fits-all approach.

  * <p>

  * @author Richard Easterling

  */

 public class Main extends SpringMain {

     public Main() {

         this.setConfigFile("classpath:RevGenSpringConfig.xml");

     }

     /**

      * Loads and runs RevGen using Spring configuration file.  RevGen is started by invoking 

      * the <code>pipeline</code> bean.

      * <p>

          * @param args takes an optional Spring XML configuration file location and/or a properties file.

      * Files can be any valid URL or classpath location.  File types are recognized by their extension,

      * names and order are not important. Here are some valid examples:

      * <ul>

      * <li>file:src/revgen/RevGenSpringConfig.xml</li>

      * <li>classpath:RevGenSpringConfig.xml</li>

      * <li>file:src/revgen/revgen.properties</li>

      * <li>classpath:revgen.properties</li>

      * </ul>

          */

         public static void main(String[] args) throws Exception {

         Main main = new Main();

         main.setArgs(args);

         main.runPipeline();

         }

 }