Sam
Sam
Hi, Please can you clarify what you mean by ip-endpoint? Connector only supports defining DDS entities (Participants, Publishers, Subscribers, Topics, DataReaders, DataWriters) in XML format. You can also specify the...
What language binding are you using (Python, JavaScript, Go,...)? Right now there is no officially supported solution for this, but people have been able to get it to work following...
Transferring this to connextdds-py repo, since you are talking about a different product
Hey @kimakuma Can you share the XML file with me? It looks like Connector is failing to parse it for some reason.
@kimakuma Thanks. So I can see a few things: 1. Looks like you are missing the top level `dds` XML tags (e.g.: https://github.com/rticommunity/rticonnextdds-connector-py/blob/master/examples/python/ShapeExample.xml#L10). 2. I don't see a the type...
Hey @Hongbo-Miao , Can you send me the QoS file you are using the load Connector?
Hey check out these two tests: https://github.com/rticommunity/rticonnextdds-connector-py/blob/100fcc307091491efb17b165ee0684ec4fcb0c38/test/python/test_rticonnextdds_data_access.py#L714-L716 https://github.com/rticommunity/rticonnextdds-connector-py/blob/100fcc307091491efb17b165ee0684ec4fcb0c38/test/python/test_rticonnextdds_data_access.py#L724-L731
Change looks good, validation failing because the native libs don't yet have the implementation of return_loan
Do you also plan to make a similar PR in JS?