Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365854

Summary:	Multiplicity of IDataModelEntity associations and multi-valued IDataModelAttributes
Product:	z_Archived	Reporter:	Andi Bur <andi.bur>
Component:	Scout	Assignee:	Project Inbox <scout.core-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Andi Bur

2011-12-07 04:47:32 EST

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

Comment 1 Andi Bur

2011-12-07 13:24:10 EST

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

Comment 2 Matthias Zimmermann

2012-07-09 06:49:21 EDT

ticket closed.
deliverd as part of eclipse scout 3.8.0 (juno release train)