![]() |
![]() |
![]() |
![]() |
![]() |
The SALT WSDL generator (tmwsdlgen) generates WSDL 1.1 specification compliant WSDL documents that can be published to most standard UDDI servers.Table 1 lists certified Web service client toolkits that are interoperable with SALT.
SALT supports most external Web service applications that are described using WSDL 1.1 standard documents with the exceptions listed in Table 2.
RPC/literal message style GWWS servers support only RPC/encoded and document/literal SOAP message style for outbound services. If RPC/literal message style is defined in the external WSDL file, the converted non-native WSDF file cannot be accepted by SALT configuration compiler. WSDL 1.1 specification defines HTTP GET & POST binding besides SOAP binding. HTTP GET & POST binding describes the interaction between a Web browser and a Web server using simple HTTP protocols.Although the GWWS server supports HTTP transport, only SOAP protocol compliant XML messages are supported on the wire. If a WSDL document contains a HTTP GET & POST binding, this binding is ignored by the SALT WSDL converter. SALT WSDL converter does not support <soap:header> and <soap:headerfault> descriptions in the WSDL 1.1 document. All <soap:header> and <soap:headerfault> messages defined for the wsdl operation are ignored by SALT WSDL converter. Table 3 lists certified Web service servers that are interoperable with SALT.
SALT supports most external Web service applications that are described using WS-TX standard documents as listed in Table 4.
Table 4 WS-TX Standards Interoperability Table 5 lists the SALT supported SAML standards and application server.