Usage:
     <ant.doc output.dir="${root.doc}/antlibdoc" javadoc.dir="../api" java.model="${out}/reverse.java.xmi" work.dir="${work}">
       <fileset dir="util/src/xml">
         <include name="**/antlib.xml" />
       </fileset>

       <fileset dir="mdr/src/xml">
         <include name="**/antlib.xml" />
       </fileset>
     </ant.doc>
     

DTD input module

This input module accepts DTDs as defined by the XML 1.0 Recommendation.

It accepts the following INPUT parameters:

W3C XML Schema output module

This output module outputs an W3C XML Schema as defined by the XML Schema Recommendation.

It supports the following OUTPUT parameters:

It has the following limitations:

• it may generate schemas that violate W3C XML Schema's restrictions on ambiguous content models;
• it may generate schemas that violate W3C XML Schema's restrictions on consistent element types;
• when the RELAX NG schema cannot be represented by W3C XML Schema, a generalization is generated; it should give a warning in this case, but does not always do so.

Annotations can be added to the RELAX NG schema to guide the translation. These annotations have the namespace URI http://www.thaiopensource.com/ns/relaxng/xsd. This document will use the convention that the prefix tx refers to this namespace URI; in other words, it will assume a namespace declaration of

xmlns:tx="http://www.thaiopensource.com/ns/relaxng/xsd"

Currently, only one annotation is supported, an attribute tx:enableAbstractElements. The value of this must be true or false. It applies to RELAX NG define elements. Trang has the ability to translate a define that contains a choice of element patterns into an abstract element declaration, which will be used as the head of a substitution group whose members are the elements in the choice. Whether it does this is determined by the value of the tx:enableAbstractElements annotation attribute. If the value is true, it will attempt to use an abstract element element. If the value is false, it will not, which means the define will typically be translated into a group definition.

 Usage:
   <reverse.ant
     output="..."/>
 

1. The comments before the type/task/macro def statement are adopted as comments of the defined object
2. The comments before the attribute/element definition are adopted as documentation of the
3. Any explicit descriptions are added after any explicit comments
4. The typdef/taskdef/macrodef way of defining the result class are set as its stereotype
5. The implementation class of typdef/taskdef is represented as a superclass of the defined model element
6. Any default values are set as default attribute values
7. Each script reverse engineered is represented as a package, following the file path to it, whereas the file name, without the extension, is stored as package name
8. For each script reverse engineered, the corresponding package contains its name assigned as a tagged value with tag = 'file.name'

Usage:

   <reverse.db
     url="jdbc:oracle:thin:&atlocalhost:1521:vegas"
     user="..."
     password="..."
     driver="oracle.jdbc.driver.OracleDriver"
     schema="..."
     output="..."/>
 

Conventions for the model produced:

1. The database column types are converted to DataType instances named: <type name>[_<column size>[_<column precision>]]. Additionally as tagged values named TAG_VALUE_DATA_TYPE_SIZE and TAG_VALUE_DATA_TYPE_PRECISION these values are bound to the concrete data type.
2. The TAG_VALUE_DATA_TYPE_PRECISION tagged value is optional. When not provided, the precision should be treated as 0
3. The TAG_VALUE_DATA_TYPE_SIZE tagged value is mandatory.
4. Any comments found while reverse engineering the database are bound as 'documentaion' tagged values. These tagged values are compatible with the Rose's approach to documentation. They are optional.
5. Each attribute created might have TAG_VALUE_NULLABLE tagged value assigned. When provided it contains 'false' to indicate attributes that cannot be null. True values are not provided.
6. Each attribute pertaining to the table's primary key is bound a 'primary_key' tagged value Its value is the sequence order of the column in the tible's primary key.

      Usage:

      <reverse.java output.file="${out}/reverse.java.xmi" target.classpathref="classpath">
        <packageset dir="util/src/java" defaultexcludes="yes">
          <include name="**" />
        </packageset>

        <packageset dir="mdr/src/java" defaultexcludes="yes">
          <include name="**" />
        </packageset>

      </reverse.java>
      

Usage:

   <reverse.xsd output="...">
     <fileset .... />
   </reverse.xsd>  
 

• The model elements (classes, association names) that represent elements in the output XML are marked with <<element>> stereotype
• For representation purposes local types (UML classes) could be introduced for XSD groups, unions, local / inlined types. All of them are marked with <<local type>> stereotype
• The column types are converted to DataType instances named: <type name>[_<column size>[_<column precision>]]. Additionally as tagged values named TAG_VALUE_DATA_TYPE_SIZE and TAG_VALUE_DATA_TYPE_PRECISION these values are bound to the concrete data type.
• The TAG_VALUE_DATA_TYPE_PRECISION tagged value is optional. When not provided, the precision should be treated as 0
• Any comments found while reverse engineering the XSD are bound as 'documentation' tagged values. These tagged values are compatible with the Rose's approach to documentation. They are optional.