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