-
Key: SDO11-6
-
Legacy Issue Number: 6655
-
Status: open
-
Source: Fraunhofer FOKUS ( Raju Nanda Vaidya)
-
Summary:
The descriptions about get/setMembers() are not correct. See Sections 2.3.7 (4) and (5). Semantics of setMembers() should be described clearly. See Sections 2.3.7 (5). Need to make it clear how these operation behaves if it is called when an Organization has already had some SDOs in the members attribute. The name of setMembers() implies that the operation replaces the existing SDOs (members) with new ones (i.e. removes the existing ones). However, the table description in Sections 2.3.7 (5) says “SDOs to be added”. This implies that existing ones are preserved and new ones are added. Which semantics do we take? (1) replacing SDOs or (2) adding SDOs? The option (1) is simpler, and (2) is semantically richer. If we go for (2), we need to think if we need to define removeMember() or removeMembers() (this is a technical revision issue, though). Proposed resolution is: replacing SDOs
-
Reported: SDO 1.0 — Mon, 1 Dec 2003 05:00 GMT
-
Updated: Wed, 11 Mar 2015 11:15 GMT
SDO11 — The descriptions about get/setMembers() are not correct
- Key: SDO11-6
- OMG Task Force: Super Distributed Objects 1.1 RTF