Community
Participate
Working Groups
1. An IDataModelEntity can have associations to other IDataModelEntities. It is currently not possible to describe the multiplicity of this relation. They are all assumed to be one-to-many or many-to-many. One-to-one and many-to-one associations cannot be modeled. An additional property fixes this issue. Distinguishing between one-to-many or many-to-many and one-to-one or many-to-one is sufficient. 2. The IDataModelAttribute.getType() describes the contents of an attribute and its representation in the GUI. However it does not define whether its content is single- or multi-valued. A new property isMultiValued fixes this problem. The default implementation is based on the different attribute types. The following are considered multi-valued by default: DataModelConstants.TYPE_CODE_LIST DataModelConstants.TYPE_CODE_TREE DataModelConstants.TYPE_NUMBER_LIST DataModelConstants.TYPE_NUMBER_TREE
implemented as described. Added additional methods on DataModelUtility o to resolve an entity path into an external id and vice versa o to sort an array of IDataModelEntity and IDataModelAttribute, respectively
ticket closed. deliverd as part of eclipse scout 3.8.0 (juno release train)
