Applies to ReadyAPI 3.10, last modified on October 07, 2021

This topic describes WSDL-specific options you can configure for your project.

To configure the options:

  1. Click on the ReadyAPI toolbar.

  2. Select WSDL in the left part of the ReadyAPI Preferences window and configure the necessary options.

The available options and their descriptions are in the table below.

Option Description
Cache WSDLs If this option is true, ReadyAPI stores the web service definitions in a local cache to avoid unnecessary loading when you open your projects and work with them. If the option is false, the definitions will be loaded from their location every time you open a project in ReadyAPI.
The option affects the following definitions:
  • WSDL
  • WADL
  • OpenAPI and Swagger definitions included in your project in ReadyAPI 2.2 and later

The option does not affect RAML definitions and Swagger definitions included in your project in ReadyAPI 2.1 and earlier.

Sample values If selected, sample values are generated in requests created by using a schema.
Type comment If selected, ReadyAPI generates comments with type information in new requests.
Include optional If selected, optional elements are always included in generated requests.
Pretty print If selected, ReadyAPI uses line feeds and indentation to display XML data of responses. If not selected, ReadyAPI displays XML contents as they are.
Attachment parts If selected, part elements are generated in request messages for MIME attachments in RPC messages (required by some WS stacks).
No Content-Type validation If selected, ReadyAPI does not validate the content type of a mime-attachment element against the type or types specified in SOAP Binding.
Schema directory Specifies a directory containing schema XSD files that should be automatically added when parsing or validating WSDL or requests. If you change the contents of this directory, you will have to restart ReadyAPI.
Name with binding If selected, ReadyAPI Test assigns names to imported interfaces based on the name of the corresponding soap/http binding. Otherwise, it uses portType. This ensures that WSDL containing bindings for both SOAP 1.1 and SOAP 1.2 will get unique names when importing.
Excluded types A list of XML Schema types and global elements in the form of name@namespace that ReadyAPI ignores when generating sample requests and responses as well as input forms in the Form editor.
By default, the XML Schema root element is added since it is quite common in .NET services. It generates a sample XML fragment of about 300 KB.
Strict schema types If selected, ReadyAPI does not use schema type redefinitions in included or imported xsd:s for a specific WSDL.
Note: The option is enabled by default in ReadyAPI versions prior to 1.7.5.
Compression limit The minimum size of messages to compress. Compressed messages have the .zip extension. The result is a base64-encoded value that is saved in the project file. For large requests, this can save up to 90% of the file space, but the requests will no longer be readable.
Pretty print project files If selected, ReadyAPI saves project files in the pretty print format to make it easier to work with a source-control system. Be aware that if you select this option, the size of the project files will increase significantly. Cached WSDLs and XSDs will also have that format. Default: Selected.

We recommend that you enable this setting if you add your project to a Git repository. The setting will make project files friendlier to the “auto-merge” feature of Git.

Trim WSDL If selected, empty spaces at the beginning and at the end of WSDL files are removed.

See Also

About WSDL

Highlight search results