-
Key: DDS11-48
-
Legacy Issue Number: 8383
-
Status: closed
-
Source: ADLINK Technology Ltd ( Hans van't Hag)
-
Summary:
DomainParticipants , being entities, can be both enabled or disabled.. Because the DomainParticipantFactory is not an entity and therefore does not have a QoS, it doesn't support a Factory QosPolicy which specifies how to create a DomainParticipant (either enabled or disabled).
Resolution:
Add a DomainParticipantFactoryQos policy to the DomainParticipantFactory, and add the operation set_qos() and get_qos() to the DomainParticipantFactory class. (However, do not make the DomainParticipantFactory an Entity itself!)
Revised Text:
In section 2.1.2.2.2, add the get_qos and set_qos methods to the table. Create two new sections (2.1.2.2.2.7 and 2.1.2.2.2.8), which explain the semantics of these get_qos and set_qos. Also explain that the fact that although the DomainParticipantFactory has a qos, it is not an Entity, since it does not have any StatusConditions or Listeners and cannot be enabled.
Add to the table in section 2.1.3 for the ENTITY_FACTORY policy in the "Concerns" column also the DomainParticipantFactory.
Add to the IDL in section 2.2.3 the following things:struct DomainParticipantFactoryQos
{ EntityFactoryQosPolicy entity_factory; };
interface DomainParticipantFactory
{ .. ReturnCode_t set_qos(in DomainParticipantQos qos); ReturnCode_t get_qos(inout DomainParticipantQos qos); };
-
Reported: DDS 1.0 — Fri, 25 Feb 2005 05:00 GMT
-
Disposition: Resolved — DDS 1.1
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS11 — (T#57) Enable status when creating DomainParticipant
- Key: DDS11-48
- OMG Task Force: Data Distribution Service RTF