Issue 18499: DDS_TopicBase connector lacks type_name (dds4ccm-ftf)
Source: Remedy IT (Mr. Johnny Willemsen, jwillemsen(at)remedy.nl)
Nature: Revision
Severity: Significant
Summary: When registering a topic to DDS we need to use an unique combination of domain id, topic name, and typename. Recent discussions revealed that there is no standard for a default typename, but also there could be reasons why an user don't want to use the default type_name. We propose to add to the DDS_TopicBase connector a type_name attribute, which when set, will be used as type_name, if not set, the DDS vendor default type_name will be used for the topic type
Resolution: 
Revised Text: 
Actions taken:
February 24, 2013: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 24 Feb 2013 14:31:59 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-Tracker: AAAAAA==


*******************************************************************************
Name:            Johnny Willemsen
Employer:        Remedy IT
mailFrom:        jwillemsen@remedy.nl
Terms_Agreement: I agree
Specification:   DDS for Lightweight CCM (DDS4CCM)
Section:         7.3.1
FormalNumber:    formal/2012-02-01
Version:         1.1
Doc_Year:        2012
Doc_Month:       February
Doc_Day:         20
Page:            20
Title:           DDS_TopicBase connector lacks type_name
Nature:          Revision
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


When registering a topic to DDS we need to use an unique combination of domain id, topic name, and typename. Recent discussions revealed that there is no standard for a default typename, but also there could be reasons why an user don't want to use the default type_name. We propose to add to the DDS_TopicBase connector a type_name attribute, which when set, will be used as type_name, if not set, the DDS vendor default type_name will be used for the topic type