9. Release Notes¶
9.1. Supported Platforms¶
Web Integration Service can be used on all supported platforms except QNX and VxWorks. For information on supported platforms, see Section 2.1 in the RTI Connext Core Libraries Release Notes for this release.
For backward compatibility information between the current and previous releases of Web Integration Service, please see the Migration Guide on the RTI Community portal.
9.3. What’s New in 7.0.0¶
9.3.1. Access to builtin topics through REST API¶
Now you can access publication, subscription, and participant builtin topics’ data through a REST API. It is no longer necessary to create a separate DDS application in order to retrieve discovery information and send it to Web Integration Service through different user-created topics.
9.3.2. Logging for on_publication_matched/on_subscription_matched and on_liveliness_lost/on_liveliness_changed¶
By enabling verbosity level 5 in Web Integration Service, you can see in the console when a publication or subscription has been matched, and when liveliness has been lost or changed.
9.3.4. Changes to Floating point values in Complex Example to avoid inconsistencies¶
The floating point numbers in the Complex Example have been replaced with numbers that can be represented without any issues. Previously, some of the numbers in the example did not have an exact floating point representation, which could cause confusion.
9.3.5. CivetWeb libraries separated from Web Integration Service executable¶
The CivetWeb libraries have been separated from Web Integration Service. These external third-party libraries, libcivetweb and libcivetweb-cpp, are now dynamically linked by the Web Integration Service executable.
9.3.6. Third-party software upgrades¶
The following third-party software used by Web Integration Service has been upgraded:
For information on third-party software used by Connext products,
see the “3rdPartySoftware” documents in your installation:
9.4. Known Issues¶
For an updated list of critical known issues, see the Critical Issues List on the RTI Customer Portal at https://support.rti.com/.
9.4.1. Configurations and their applications cannot use same name¶
Due to current limitations in Connext DDS’s XML Parser, the name of the Web Integration Service configuration tag and the name of the applications within that configuration cannot be the same. For example:
<web_integration_service name="ShapesDemo"> <application name="ShapesDemo"/> </web_integration_service>
To workaround this limitation, use different names for the service configuration tag and the applications within. For example:
<web_integration_service name="ShapesDemo"> <application name="ShapesDemoApplication"/> </web_integration_service>
[RTI Issue ID CORE-3542]