| Previous | Table of Contents | Next |
If a WSDL specification is the result of translation of an OMG IDL specification, then the reverse mapping from that translated
WSDL specification should be the original IDL specification.
To accomplish this, the IDL to WSDL translation specified by the CORBA to WSDL/SOAP Interworking specification provides a
hint, in the form of an XML schema annotation giving both a reference to the source IDL and the version of the mapping used.
Hints may be provided that refer to the source IDL file, or to the repository ID for a given generated construct (including
any prefixes defined by a #pragma prefix directives).
The reverse translation from WSDL to IDL would use this hint to shortcut the translation process by having the original IDL
specification be the reverse translation from the WSDL.
This will avoid round trip divergence of the IDL specifications associated with a WSDL service, which would result using the
WSDL to IDL mapping translations to generate a new IDL specification associated with the WSDL output from the CORBA to WSDL-SOAP
mapping specification.
The interaction translation mechanisms required to support a CORBA Client accessing a WSDL Port differ depending on the origin
of the port definition.
In particular, an implementation of this specification may encounter a WSDL port type that resulted from a translation of
an IDL definition. When that happens, the interaction translation mechanisms, defined in this specification, to support a
CORBA client accessing such a WSDL Port are inappropriate. The appropriate mechanisms are similar to those required to support
a CORBA server sending a response to a WSDL port for an Operation that originated as an IDL interface operation. These translation
mechanisms are specified in the CORBA to WSDL/Soap specification (formal/03-11-02).
Note – Since the interaction time translation mechanisms to support this reverse specification translation option are different
than those designed to support specifications originating as WSDL port types, this feature is an optional conformance point
for this specification.