...

Support for state tree cycles of non-field entities is under consideration in future versions of the platform.  

Collections

Lists

At present, the Application Data Modeler does not provide support for Lists. Applications are instead encouraged to use the Queue collection type instead. 

Generic Collections Support

Collections in the state model are defined in the <collections> element of a model. Each collection is generated with its own unique Java type that extends a standard Java Collection. This modeling construct is useful from a support perspective because it makes it easy to identify the collection and makes it easier to configure specific collection types. 

A feature under consideration for a future version of the platform would allow ADM models to forego creating specific collection types and would instead allow collection component types to be declared in field definitions as shown below. 

<entity name="MyEntity" factoryid="1" id="1">
  <field name="myList" type="List{CollectionObject}"/>
  <field name="mySet" type="Set{CollectionObject}"/>
  <field name="someMap" type="Map{CollectionObject, MapEntry}"/>
  <field name="aQueue" type="Queue{CollectionObject}"/>
</entity>
 
<entity name="CollectionObject" factoryid="1" id="2">
  <field name="value" type="Integer" />
  <field name="comment" type="String" />
</entity>
<entity name="MapEntry" factoryid="1" id="2">
  <field name="value" type="Integer[]" />
</entity>

Primitive Collections

It is not currently possible to define collections with primitive value types. Adding support for this is currently under consideration. 

Inheritance and Polymorphism

...