DDS11 — (R#136) Additional operations allowed on disabled entities

The specification states that before an entity is enabled, the only operations that can be invoked on it are get/set listener, get/set QoS, get_statuscondition, and factory methods. This list is unnecessarily restrictive.

Proposed Resolution:

The following operations should also be allowed:
· TopicDescription::get_name
· TopicDescription::get_type_name
· DomainParticipant::lookup_topicdescription
· Publisher::lookup_datawriter
· Subscriber::lookup_datareader
· Entity::get_status_changes and all get_*_status operations. Note that no status is considered 'triggered' when an Entity is disabled.
· All get_/set_default_*_qos operations

Proposed Revised Text:

Revise the fourth paragraph of section 2.1.2.1.1.7 enable to read:
If an Entity has not yet been enabled, the following operations may be invoked on it in general:
· Operations to set or get an Entity's QoS policies (including default QoS policies) and listener
· get_statuscondition
· 'factory' operations
· get_status_changes and other get status operations (although no status of a disabled entity is ever considered changed)
· 'lookup' operations

Other operations may explicitly state that they may be called on disabled entities; those that do not will return the error NOT_ENABLED.

Add the following sentence to sections 2.1.2.3.1.2 (TopicDescription::get_type_name) and 2.1.2.3.1.3 (TopicDescription::get_name): "This operation may be invoked on a Topic that is not yet enabled or on a ContentFilteredTopic or MultiTopic based on such a Topic."

No Data Available