WSDL Importer

Tuning Importer behavior

The WSDL Importer has a Java™ native interface and uses the JVM options specified in the dtx.ini file to create a Java virtual machine (JVM). For information about configuring JVM options to tune the importer's behavior, see "Configuring JVM options from the dtx.ini file" .

Import options

The WSDL import process can create a classic type tree or a native XML schema (.xsd) file from the WSDL document. You select the type of output in the WSDL Importer wizard.

• When the WSDL document structure requires support for derived types (such as through the xsi:type attribute), create a native XML schema.
• When the WSDL document structure does not require support for derived types, create a classic XML type tree. Classic type trees are smaller than native XML schemas.

Classic type tree processing

The importer reads a WSDL document and assembles lists of port types, operations, services, messages, and bindings. When the parsing is complete, the importer creates a map for each web service operation and adds it to the resulting XML map source file. During this process, the XML Schema Importer is used to create the types defined in the input WSDL document.

After the WSDL Importer imports the WSDL document, it creates a WSDL type tree (.mtt) file and an XML (*_map.xml) file. Use File > Import > Map from XML in the Design Studio to import the XML file to create a map. The import process creates a map ( WSDLname.map.mms) that uses the new WSDL type tree in the output cards.

Native XML schema processing

WSDLname.xsd

Contains the XSD and WSDL-based schema types.

WSDLname_soap.xsd

Contains the SOAP envelope, header, and body types.

Use the WSDLname_soap.xsd as the card's native type tree.