Replies: 1 comment
-
Hi @lexamor , Currently, configuring DataRepresentationQosPolicy from XML is not supported. We will work on it in future releases. If you manage to fix the problem, fill free to make a PR. For further help, please contact us directly to info@eprosima.com for further work on this issue if this is a need for your project. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there an already existing issue for this?
Expected behavior
Configuration of the endpoints should be allowed independently of the chosen discovery mechanism.
Current behavior
If DataRepresentationQosPolicy is configured on the endpoints (e.g. using C++) (DataReader and DataWriter), but not configured by the STATIC EDP XML profile, endpoints discovery is not happened.
But since XML configuration of this QoS is not supported at this time, seems there is no way to manage this use case.
Steps to reproduce
Configure DataRepresentationQosPolicy for the endpoints and choose the static discovery.
Build & run demo app
As a result discovery is not finished, and appropriate incompatible QoS callbacks are triggered.
DDSStaticHelloWorldExample could be used as a test app, appropriate patch is provided
Fast DDS version/commit
2.14.4
Platform/Architecture
Ubuntu Focal 20.04 amd64
Transport layer
Default configuration, UDPv4 & SHM
Additional context
XML configuration file
Relevant log output
Network traffic capture
No response
Beta Was this translation helpful? Give feedback.
All reactions