The host of an API stores the information about where the API is located. You can add schemes change the base URL and the base path. This way, JOSF reuses this information for when the actual request is executed.
|-1-|   |----------2---------||--3--||----4----|

  1. The scheme. Often HTTP or HTTPS. JOSF automatically separates the scheme with the base URL by adding a `://` in between.
  2. The base URL of the application under test
  3. The base path where the service is located
  4. The resource path where a specific resource is located

Hosts can be created manual, or imported by a service definition, when adding a new host.

Importing service definition

JOSF accepts three types of service definition files;

  • WSDL
  • Swagger 2.0
  • OpenAPI / Swagger 3.0

You can provide the service definition URL or the actual raw definition. Either way, JOSF will process the service definition into a new host, with the correct resources.

XSD import references

When using a WSDL, it could happen that the WSDL requires certain XSD files to model the actual requests. You can validate whether your WSDL file requires XSD files, when there is an import statement in the WSDL file, looking something like this;

<xsd:import schemaLocation=”your-model.xsd” namespace=”my-namespace”/>

In this case, the XSD file your-model.xsd, is imported during the processing of the WSDL.

Before importing the WSDL, you’ll need to add each referred import XSD file to the `C:\Program Files\JOSF\api` directory. This way, during the processing of the WSDL file, JOSF is able to find the referred imported files and create the correct models based on those XSD files. After the import is successful, you can remove the XSD files again.

In this document