RTI Connext Migration Guide
6.0.1
1. Upgrade Overview
1.1. Upgrade Path
1.2. Upgrade Steps
2. Upgrading from 6.0.0 to 6.0.1
2.1. General Compatibility 6.0.1
2.1.1. Platforms
2.1.2. Wire Changes and Compatibility
2.1.2.1. Fragmentation is now independent of sample serialized size
2.1.3. Type System Compatibility
2.1.3.1. Wire representation of TypeObject
2.1.3.2. Incompatibility issues for Java and .Net when using XCDR2
2.1.4. Other Compatibility Issues
2.1.4.1. Large data support for Multichannel and TopicQuery has been disabled
2.2. Product-Specific Compatibility 6.0.1
2.2.1. RTI Connext DDS Core Libraries
2.2.2. RTI Code Generator
2.2.2.1. Incompatibility issues for Java and .Net when using XCDR2
2.2.2.2. Invalid XSD file from an IDL/XML file if input file contains a range annotation
2.2.3. RTI Connext DDS Micro
2.2.4. RTI Security Plugins
2.2.4.1. OpenSSL upgrade
2.2.4.2. Changes to building an application
2.2.4.3. Changes to behavior of intermediate certificates
2.2.4.4. Property key_material_key now required for Secure Persistence Service
2.2.5. RTI Secure WAN Transport
2.2.5.1. OpenSSL upgrade
2.2.5.2. Changes to building an application
2.2.6. RTI TLS Support
2.2.6.1. OpenSSL upgrade
2.2.6.2. Changes to building an application
3. Upgrading from 5.3.1 to 6.0.0
3.1. General Compatibility 6.0.0
3.1.1. Platforms
3.1.2. Wire Compatibility
3.1.2.1. RTPS Versions
3.1.2.2. New default GUID generation mode
3.1.2.3. Default shared memory locator has changed
3.1.2.4. 4.2e alignment option deprecated
3.1.2.5. Changed wire representation of TypeObject
3.1.2.6. TypeCode information is not sent by default
3.1.3. Reliability Protocol
3.1.3.1. Changes in behavior of write() operation with KEEP_LAST configuration
3.1.4. Type System Compatibility
3.1.4.1. Migration to Extended CDR encoding version 2 (XCDR2)
3.1.4.2. Changed wire representation of TypeObject
3.1.4.3. TypeCode information is not sent by default
3.1.4.4. Unbounded sequences and strings in XML type representation
3.1.4.5. wchar and wstring language binding changes
3.1.4.6. Properties dds.type_consistency.ignore_member_names and dds.type_consistency.ignore_sequence_bounds have been deprecated
3.1.5. Transport Compatibility
3.1.5.1. Default shared memory locator has changed
3.1.5.2. VxWorks shared-memory transport compatibility
3.1.6. XML Compatibility
3.1.6.1. QoS Profile multiple inheritance
3.1.6.2. XSD issues
3.1.7. Other Compatibility Issues
3.1.7.1. Behavior change when retrieving QoS using topic_name (when there are multiple matching QoSes)
3.2. Product-Specific Compatibility 6.0.0
3.2.1. RTI Connext DDS Core Libraries
3.2.1.1. Application Binary Interface
3.2.1.2. APIs
3.2.1.3. Generated Code
3.2.1.4. QoS
3.2.1.5. Library Size
3.2.1.6. Memory Consumption
3.2.1.7. Performance
3.2.1.8. RTI Connext DDS Micro Compatibility
3.2.2. RTI Security Plugins
3.2.2.1. Configuration
3.2.2.2. Wire Compatibility
3.2.2.3. APIs
3.2.3. RTI Secure WAN Transport
3.2.4. RTI TLS Support
3.2.5. RTI Ada Language Support
3.2.5.1. APIs
3.2.6. RTI Code Generator
3.2.6.1. Removed -stl Option
3.2.6.2. Removed Support for -notypecode
3.2.6.3. Removed -use42eAlignment
3.2.6.4. Generated code for Extended CDR Encoding Version 2 (XCDR2)
3.2.6.5. Incorrect TypeCode name for member fields whose name was a keyword in Java
3.2.6.6. Modified maximum length of sequences and strings when -unboundedSupport is not used, when converting to XML
3.2.6.7. Traditional C++ compiled with -fno-exceptions
3.2.6.8. Support for new, standard IDL, fixed-width integer types
3.2.6.9. Change in default optimization level for code generation
3.2.7. RTI Connext DDS Micro
3.2.7.1. New Installation Procedure
3.2.7.2. Change In Documentation
3.2.7.3. Application Binary Interface
3.2.7.4. APIs
3.2.7.5. Connext DDS Compatibility
3.2.8. RTI Routing Service
3.2.8.1. Application Binary Interface
3.2.8.2. APIs
3.2.8.3. Configuration
3.2.8.4. Administration and Monitoring
3.2.8.5. QoS
3.2.8.6. Performance
3.2.8.7. Library Size
3.2.8.8. Documentation
3.2.9. RTI Recording Service
3.2.9.1. APIs
3.2.9.2. Configuration
3.2.9.3. Database Format
3.2.9.4. Running Recording Service 5.3.1
3.2.9.5. Documentation
3.2.10. RTI Persistence Service
3.2.10.1. External Database Compatibility
3.2.10.2. Persistent Storage (Database) Format Compatibility
3.2.10.3. Persistence Storage (Database) Locking Compatibility
3.2.10.4. Dynamically Linked Libraries
3.2.11. RTI Database Integration Service
3.2.11.1. Database Compatibility
3.2.12. RTI Cloud Discovery Service
3.2.13. RTI Launcher
3.2.13.1. Configuration
3.2.14. RTI Administration Console
3.2.14.1. New Default GUID Generator Mode
3.2.14.2. New GTK+ and Cairo Dependencies
3.2.14.3. Connext DDS Micro Compatibility
3.2.15. RTI Monitor
3.2.16. RTI Utilities
3.2.16.1. Dynamically Linked Libraries
4. Regressions
4.1. 6.0.1 Regressions
4.1.1. RTI Prototyper
4.2. 6.0.0 Regressions
4.2.1. RTI Connext DDS Core Libraries
4.2.1.1. Fixed in 6.0.1
4.2.1.2. Not Fixed in 6.0.1
4.2.2. RTI Security Plugins
4.2.2.1. Fixed in 6.0.1
4.2.3. RTI Code Generator
4.2.3.1. Fixed in 6.0.1
4.2.4. RTI Routing Service
4.2.4.1. Fixed in 6.0.1
4.2.4.2. Not Fixed in 6.0.1
4.2.5. RTI Recording Service
4.2.5.1. Fixed in 6.0.1
4.2.6. RTI Cloud Discovery Service
4.2.6.1. Fixed in 6.0.1
5. Changes to This Document
6. Copyrights
RTI Connext Migration Guide
Docs
»
3. Upgrading from 5.3.1 to 6.0.0
»
3.2. Product-Specific Compatibility 6.0.0
»
3.2.12. RTI Cloud Discovery Service
View page source
3.2.12. RTI Cloud Discovery Service
ΒΆ
See
Section 4.2.6
for regressions related to
Cloud Discovery Service
in release 6.0.0.