This is an abstract of a demo that RTI plans to have available at the RTI Connext Users Group meeting, to be held in London next month (http://www.rti.com/connextcon).
Working with structured data, each domain (Enterprise, Real-Time, Java ESB, etc.) will have its preferred method or defined structure for in-memory, and for stored data instances. The fun is when you move across the boundaries from one domain to another, or when you want to leverage one standard’s structures within a non-native domain.
The W3C consortium defines a Document Object Model to hold data in-memory, as well as XML and the Schema-for-Schemas, XSD, used when you want to serialize the data and communicate it to a third party. In OMG DDS, the equivalents are the Dynamic Data Object and Type-specific object PSMs, and RTPS serialization when transmitting instances.
Various ways to leverage the W3C standards in an RTI Connext DDS environment are demonstrated, including:
- DCPS Discovery information to XML, useful for:
- Self-documenting DDS Domains
- Capturing snapshots of what is on a DDS Domain
- Discovered Type information to XSD or XML, useful for:
- Auto-generated Type info, formatted as XML for use with RTI Tools that can read XML-defined Types
- Auto-generated XML Schema Documents, for XML files that can be used to pre-load instances with specific information (‘Configuration Propagation’, ‘Test’, and other use-cases)
- Generating XSD information for use by Enterprise tools (that can’t read IDL)
An example Java application is demonstrated, that uses DCPS Discovery Topics to generate XML and XSD files, as well as show how to read in XML files for use by DDS applications, either for remote configuration (when published as Last-Value-Cache for example), or for pre-loading Type instances for publication via:
ShapeTypeExtended steInstance =