2.1 Overview of Data Type Mapping and Message Conversion
SALT supports bi-directional data type mapping between WSDL messages and Oracle Tuxedo typed buffers. For each service invocation, the GWWS server converts each message between Oracle Tuxedo typed buffers and SOAP message payloads. A SOAP message payload is the XML effective data encapsulated within the <soap:body
> element. For more information, see Understanding SALT Message Conversion
For native Oracle Tuxedo services, each Oracle Tuxedo buffer type is described using an XML Schema in the SALT generated WSDL document. Oracle Tuxedo service request/response buffers are represented in regular XML format. For more information, see Tuxedo-to-XML Data Type Mapping for Oracle Tuxedo Services
For external Web services, each WSDL message is mapped as an Oracle Tuxedo FML32
buffer structure. An Oracle Tuxedo application invokes SALT proxy service using FML32
buffers as input/output. For more information see, XML Schema Built-In Simple Data Type Mapping
SALT also supports non-SOAP data type mapping (i.e., REST over HTTP in both XML and JSON format. This is initiated when services are exposed as HTTP/REST
services. For more information, see REST Data Mapping
Parent topic: Data Type Mapping and Message Conversion