Aggregation Details
We decided to use aggregation over association for all managed items because they can be bound to a model and associations can't. The disadvantage of using an aggregation is that a managed item can only be part of one aggregation. So the instance of an extendedNumberFormat can be part of an aggregation of table 1 but can't be part of an aggregation of table 2 while it is still part of table 1.
The Item of an aggregation named "sampleThing" that has a cardinality of 0...1 (and a multiplicity of 1:1) can be accessed by using one of the following methods:
- getSampleThing() - Returns the current aggregated object or null.
- setSampleThing(object) - Sets the provided object as the new aggregated object. Returns this for method chaining.
- destroySampleThing() - Destroys the current aggregated object and clears the aggregation. Returns this for method chaining.
The following aggregations are available:
| Aggregation Name | Aggregated Object Type | Cardinality | Description |
|---|
extendedNumberFormat | graphomate.ui.ExtendedNumberFormat | 0...1 | The item of this aggregation allows you to configure a special formatting of the column that overrides the number format defined by the table. If no format is set, the table's number format will be used. |