RAD Studio (Common)
ContentsIndex
PreviousUpNext
WSDL Import Options

Use this dialog box to specify information that the importer needs to connect to the server that publishes a WSDL document or to configure the way the wizard generates code to represent the definitions in a WSDL document.

Use the Connection tab page to provide information the wizard needs for connecting to the server that hosts the WSDL document.

Item 
Description 
User Name  
Specify the user name to use if the WSDL document is on a secure server that requires authentication.  
Password  
Specify the password to use with User Name when the WSDL document is on a secure server that requires authentication.  
Proxy  
Specify the host names for any proxy servers that must forward requests to the URL specified on the Source page of the Web Services Import dialog.  

Use the Code Generation tab page to configure how the importer translates between the definitions in the WSDL document and the native code that it generates.

Item 
Description 
Declare Namespace  
This option is only valid when the importer generates C++ code. When checked, it puts all generated type definitions in a C++ namespace that is named after the imported service.  
One OutParam is Return  
When checked, the importer maps operations with a single output message into functions where the output message is the return value. If this is not checked, the output message is mapped to an output parameter.  
Unwind Literal Params  
In document literal encoding, the Web Service does not describe operations. Rather, it describes two records, one that describes the expected input and one that describes the output. When Unwind Literal Params is checked, the importer converts these two records into method calls.  
Generate Destructors  
When checked, the importer generates destructors on the classes that represent types. These destructors free any nested members whose types are classes or arrays of classes. The generated destructors simplify the work you must do when freeing instances of classes that represent types, because you do not need to explicitly free class members that also use classes to represent the remotable type.  
Ignore Schema Errors  
When checked, the importer attempts to import WSDL documents that are not well-formed. Often the importer can deduce the appropriate information even when the schema is badly formed.  
Warnings Comments  
When checked, the importer adds warning messages to the comments it puts in the top of generated files. These warnings describe problems such as invalid type definitions in the WSDL document when Ignore Schema Errors is checked, problems encountered when unwinding literal parameters when Unwind Literal Params is checked, and so on.  
Emit Literal Types  
In document literal encoding, the Web Service does not describe operations. Rather, it describes two records, one that describes the expected input and one that describes the output. When Generate Literal Types is checked, the importer generates type definitions for these two records, even if it converts them to method calls (that is, even if Unwind Literal Params is checked).  
Ambiguous Types as Array  
In some cases when the WSDL document does not make consistent use of schema definitions, the importer has problems importing array types, which results in a type that is represented by a class with no members. When Ambiguous Types as Array is checked, the importer compensates by changing these empty classes to arrays. This option is always safe to use unless the WSDL document describes a Web Service that uses document literal encoding. Document literal encoding can also give rise to an empty class that represents a procedure. If you check Ambiguous Types as Array when importing a WSDL document for a Web Service that uses document literal encoding, the resulting generated code may not work.  
Generate Server Implementation  
When checked, the importer generates implementation classes for the imported interfaces. Use this option when writing a server that implements a Web Service that is already defined in a WSDL document.  
Map String to WideString  
When checked, the importer maps all string types to WideString values. When Unchecked, the importer uses the string type instead. WideString values may be required to handle values that use extended characters. If string values do not use extended characters, it is more efficient to use the string type.  
Copyright(C) 2009 Embarcadero Technologies, Inc. All Rights Reserved.
What do you think about this topic? Send feedback!