Core: extend meta model by "Ordered" flag (#340).

Both, "Composition Definition" and "Aggregation Definition" have a new boolean child type: "Ordered" (dm4.core.ordered).

COMPATIBILITY NOTE:
For a production instance a migration must be supplied that adds the "Ordered" type.

See ticket 340.
Core: refactor type construction pt.1 (#340).

Former approach:
Types are constructed with a model that is initialized only partial and then load and init the remaining parts themselfs.

New concept:
Construction of types is the responsibility of the object factory.
Loading the model and constructing the actual type object from it are strictly separated.
Never construct a type with a partly initialized model.

Does not yet work.
Do not install the "child-order" branch.

Done
    - data type
    - index modes
Pending
    - association definitions
    - label configuration
    - view configuration

In preparation of "Child Topic Order".

See ticket 340.
Core: refactor type construction pt.2 (#340).

Done
    - association definitions
Pending
    - label configuration
    - view configuration

Does not yet work.
Do not install the "child-order" branch.

In preparation of "Child Topic Order".

See ticket 340.
Core: refactor type construction pt.3 (#340).

Done
    - label configuration
    - view configuration

So, a type doesn't *load* itself anymore.
Still does not work.
It occurred a type must not *save* itself either.

Do not install the "child-order" branch.

In preparation of "Child Topic Order".

See ticket 340.
Core: refactor type storage pt.1 (#340).

Done:
    - base topic parts
Pending:
    - data type
    - index modes
    - association definitions
    - label configuration
    - view configuration

Does not yet work.
Do not install the "child-order" branch.

In preparation of "Child Topic Order".

See ticket 340.
Core: refactor type storage pt.2 (#340).

Done:
    - data type
    - index modes
    - association definitions
Pending:
    - label configuration
    - view configuration

Does not yet work.
Do not install the "child-order" branch.

In preparation of "Child Topic Order".

See ticket 340.
Core: refactor type storage pt.3 (#340).

Done:
    - label configuration
    - view configuration

Does not yet work.
Do not install the "child-order" branch.

In preparation of "Child Topic Order".

See ticket 340.
Core: refactor type storage pt.4 (#340).

Introducing a 2-level caching architecture solves a problem with cyclic type definitions.
Note: we deliberatley support cyclic type definitions.
Consider the association type "Composition Definition": it is a composite type which itself is build of Composition Definitions (here: "Include in Label" and "Ordered" boolean childs).

Does not yet fully work.
Do not install the "child-order" branch.

In preparation of "Child Topic Order" (#346).

See ticket 340.
Core: refactor type storage complete (#340).

There are still glitches.
Do not install the "child-order" branch.

See ticket 340.
Core: fix topic type default URI (#340).

There are still glitches.
Do not install the "child-order" branch.

See ticket 340.
Core: fix topic type update (#340).

See ticket 340.
Core: fix assoc def sequence update (#340).

Type API:
    - getAssocDefs() returns Collection<AssociationDefinition>      (instead of a Map)
TypeModel API:
    - getAssocDefs() returns Collection<AssociationDefinitionModel> (instead of a Map)
    - removeAllAssocDefs() is new method
    - setAssocDefs()       is removed
Dropped copy constructors:
    - TypeModel
    - TopicTypeModel

See ticket 340.