Skip to main content

Data structures

<blueprint name="">
        <type></type>
        <parameters>
        ...
        </parameters>
        <data>
            <documentData name="">
                <contentType></contentType>
                <path></path>
                <document><![CDATA[
                ...
                ]]></document>
            </documentData>
        </data>
    </blueprint>

Both "documentData" and "document" need a unique name.

All Blueprints have the root element "blueprint". The root-element has a "name" attribute, which is used as a display name in the userinterface.

The child-element "type" specifies to which type of data model it belongs to. For example, the Blueprint for creating a new Context belongs to the "neonContext" type.

The type controls where the Blueprint is located in the project-tree inside the ADITO Designer, for example in the context-menu of "context" or "entity".

Parameters are specified in the child element "parameters". The order of the parameters specifies how the elements are displayed on the GUI.

Inside the "documentData" a "contentType" and a "path" can be specified.

The "documentType" can be:

  1. MODEL for data models

  2. XML for xml-files, such as Liquibase

  3. PLAIN for files that should be created as they are written inside the "document"-element

The "path" is optional and is used to specify the directory in which the resulting file is going to be saved.

The path is absolute from the project-path, except a ".\ or "./" is given, then the path starts in the directory in which the Blueprint is executed.

The data models that should be created must be specified in the "data" element. It is possible that more than one "documentData" element is added to create multiple data models at the same time. Each "documentData" element gets an attribute "name" which is used to reference them inside a Blueprint. This "name" attribute has no effects in the resulting data models.

list​

Lists are created with the help of "|" (pipe) characters. Duplicate values are not automatically filtered. The order in a list is fixed and is defined by the order in which the values are provided.

The value of a list can be referenced as a whole with ${list} or a single value of a list with ${list.n} ("n" standing for the index of a value).

Example:

valueA|valueB|valueC

map​

When values are linked to other values, a map is used. A map is created with the help of "|" (pipe) and "=" (equal) charakters. If a value is defined twice inside a map, the previous value gets overwritten.

Example:

valueA=valueA|valueB=valueB