-
Key: DSS2-47
-
Legacy Issue Number: 5156
-
Status: closed
-
Source: MITRE ( Ms. Susan Symington)
-
Summary:
The purpose of the Commit Region Modifications service is to either create a region specification from a region template or to modify an already-existing region specification and all derived region realizations. If not all dimensions of a region template have had their range bounds set, then no region specification can be created by the Commit Region Modifications service because a region specification, by definition, has range bounds set for each dimension in the region template. Therefore, invoking the Commit Region Modifications service in this situation is considered an error. However, as currently written, the standard permits invocation of the Commit Region Modifications service in this situation. The following text is recommended to correct this problem:
Each region designator that is passed to the Commit Region Modifications service is required to be the designator of either a region template that has had the Set Range Bounds service invoked at least once for all of its dimensions, or a region specification. If a federate invokes the Commit Region Modifications service with a region designator argument that is neither the designator of a region template that has had the Set Range Bounds service invoked at least once for all of its dimensions, nor the designator of a region specification, then the Commit Region Modifications service shall throw the "Invalid region" exception.
-
Reported: DSS 1.1 — Tue, 9 Apr 2002 04:00 GMT
-
Disposition: Resolved — DSS 2.0
-
Disposition Summary:
Add the suggested text.
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DSS2 — Service 9.3: Commit Region Modifications
- Key: DSS2-47
- OMG Task Force: Distributed Simulation V2.0 FTF