DataModel

The Modello Data Model.

Here's an example of a modello data model.

<model>
  <id>myproject</id>
  <name>MyProject</name>
  <description>My Project's Data Model</description>
  <defaults>
    <default>
      <key>package</key>
      <value>org.codehaus.myproject.model</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="myproject">
      <name>Model</name>
      <version>3.0.0+</version>
      <fields>
        <field>
          <name>myfield</name>
          <version>1.0.0</version>
          <description>The example of field.</description>
          <type>String</type>
        </field>
      </fields>
    </class>
  </classes>
</model>

Top level <model>

The top level <model> must contain an <id> <name> and at least 1 <classes><class> element.

The optional <defaults> tag is commonly used to define properties that the various Modello generators use.

The <classes> section.

You can have 1 or more <class> elements within this section.

Each <class> represents a container for a set of <field>s.

Every <field> is a component in the container.

Notes on the <field> section

XML Generator Notes about <field>:

By default each <field> starts out life as an <element> with text content.
A <field> can be set to be an attribute on the <class> element by using the <field xml.attribute="true"> syntax.
field/name becomes the name of the element (or attribute key).
- field#xml.tagName can be used to change the name of the element (or attribute key)
field/version is unused.
field/description is unused.
field/type is one of the following
- boolean
- char
- double
- int
- long
- short
- date
- String
- Boolean
- DOM (currently only supported by xpp3 generators)
- Another class
field/association dictates the multiplicity of a field (1 to many, or 0 to many so far)
- generated readers and writers do not enforce the multiplicity rules (yet)
- field/association must have at a minimum the <type> element defined.
- field/association/type only refers to other <class> id's, no java primitives allowed here.
  - field/association/type will be used to determine the name of the nested elements.
  - singular form of the field tagname will be used for the nested element name.
    - s/(.*)ies$/\1y/g - "Properties" becomes "Property"
    - s/(.*(ch)?)es$/\1/g - "Branches" becomes "Branch"
    - s/(.*)s$/\1/g - "Reports" becomes "Report"
  - field/association#xml.tagName can be used to specify an overridden nested element name.
- field/assocation#xml.itemsStyle defaults to "wrapped".

Example of `field/assocation#xml.itemsStyle="wrapped"`

<!-- Model -->
<class>
  <name>example</name>
  <fields>
    <field>
      <name>components</name>
      <version>4.0.0</version>
      <association xml.itemsStyle="wrapped">
        <type>Component</type>
        <multiplicity>*</multiplicity>
      </association>
    </field>
  </fields>
</class>
<class>
  <name>Component</name>
  <version>4.0.0</version>
  <fields>
    <field>
      <name>name</name>
      <type>String</type>
    </field>
  </fields>
</class>

<!-- xml -->
<example>
  <components>
    <component>
      <name>foo</name>
    </component>
    <component>
      <name>bar</name>
    </component>
  </components>
</example>

Example of `field/assocation#xml.itemsStyle="flat"`

<!-- Model -->
<class>
  <name>example</name>
  <fields>
    <field>
      <name>components</name>
      <version>4.0.0</version>
      <association xml.itemsStyle="flat">
        <type>Component</type>
        <multiplicity>*</multiplicity>
      </association>
    </field>
  </fields>
</class>
<class>
  <name>Component</name>
  <version>4.0.0</version>
  <fields>
    <field>
      <name>name</name>
      <type>String</type>
    </field>
  </fields>
</class>

<example>
  <component>
    <name>foo</name>
  </component>
  <component>
    <name>bar</name>
  </component>
</example>

Feeds