@@ -91,6 +91,42 @@ It is advisable to check that the returned value is a valid pointer.
9191 :end-before: //!
9292 :dedent: 8
9393
94+ .. _dds_layer_domainParticipant_creation_default_profile :
95+
96+ Default profile DomainParticipant creation
97+ ------------------------------------------
98+
99+ If there is a profile already exported in the environment (please refer to :ref: `xml_profiles ` for related
100+ information), creating a DomainParticipant with the
101+ |DomainParticipantFactory::create_participant_with_default_profile-api | member function on the
102+ :ref: `dds_layer_domainParticipantFactory ` singleton would use that settings to configure the participant.
103+ If the profile has not been exported, the DomainParticipant will be created with the default values per
104+ :ref: `dds_layer_domainParticipantQos `, and ``0 `` as |DomainId-api |.
105+
106+ Optional arguments are:
107+
108+ * A Listener derived from :ref: `dds_layer_domainParticipantListener `, implementing the callbacks
109+ that will be triggered in response to events and state changes on the DomainParticipant.
110+ By default empty callbacks are used.
111+
112+ * A |StatusMask-api | that activates or deactivates triggering of individual callbacks on the
113+ :ref: `dds_layer_domainParticipantListener `.
114+ By default all events are enabled.
115+
116+ |DomainParticipantFactory::create_participant_with_default_profile-api | will return a null pointer if there was an
117+ error during the operation.
118+ It is advisable to check that the returned value is a valid pointer.
119+
120+ .. note ::
121+
122+ XML profiles must have been loaded previously. See :ref: `xml_profiles `.
123+
124+ .. literalinclude :: /../code/DDSCodeTester.cpp
125+ :language: c++
126+ :start-after: //DDS_CREATE_DOMAINPARTICIPANT_DEFAULT_PROFILE
127+ :end-before: //!
128+ :dedent: 8
129+
94130.. _dds_layer_domainParticipant_deletion :
95131
96132Deleting a DomainParticipant
0 commit comments