-
Key: DDS12-49
-
Legacy Issue Number: 9531
-
Status: closed
-
Source: THALES ( Virginie Watine)
-
Summary:
XML mapping file does not allow you to define both the Topic name and the Topic type_name separately
Summary:
In the DCPS, there is a clear distinction between a topic name and a topic type. (Both names must be provided when creating a Topic). However, the DLRL mapping XML only allows us to specify one name attribute which is called ‘name’. It is unclear whether this name should identify the type name or the topic name. Currently we just have to assume that the topic name and type name are always chosen to be equal, but that does not have to be the in a legacy topic model.
Proposed Resolution:
Add a second (optional) attribute to the mainTopic, extensionTopic, placeTopic and multiPlaceTopic that identifies the type name. If left out, the type is assumed to be equal to the topic name.
-
Reported: DDS 1.1 — Mon, 3 Apr 2006 04:00 GMT
-
Disposition: Resolved — DDS 1.2
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS12 — define both the Topic name and the Topic type_name separately
- Key: DDS12-49
- OMG Task Force: Data Distribution RTF 3