WSDL is one of many asset models supported by the WSO2 Governance Registry. Read more on Supported APIs & Standards for a complete list of asset models supported by WSO2 Governance Registry.
| Note |
|---|
Governance Registry does not support the WSDL 2.0 standard out-of-the-box. However, if you need this support to be available, you can extend the |
Users can upload WSDL files from users local file system as a Governance Archive (See Creating a Governance Archive) or import them from a given URL.
During the importing WSDL is validated and put into the registry. If the given WSDL requires any other WSDL imports, these WSDLs also going through the same process and are imported into the registry. All the schema/policy imports are also downloaded into the registry and put into the location where all the schemas/policies are stored.
The WSDL can have a number of endpoints. The Governance Registry creates new resources for these endpoints and puts them into a general location where all the endpoints are saved.
A single WSDL can have a number of dependent resources at the end of import process and the WSDL resource will have associations and dependencies for those resources according to the relationship.
| Info |
|---|
The registry creates service resources for all the WSDL imports by default and adds some of the useful data into the service resources by parsing the WSDL. For example, name, namespace, WSDL URL (this is the location of WSDL stored in the registry) and endpoints if available in the WSDL. |
Validating WSDLs Offline
Users can upload WSDL files to the WSO2 Governance Registry. During the uploading process, the Governance Registry validates each WSDL file during its first addition. However, in order to do that, there should be an active internet connection on the machine which is running the Governance Registry. This page explains the process to follow in order to add and validate WSDLs using Governance Registry on a machine without having an internet connection.
...
There can be problems and delays in validating WSDL, if the machine doesn't have an active internet connection at the moment. So, as a workaround for this issue, the following sections explain how to host those required resources locally and validate WSDLs using those locally hosted resources without using an internet connection:
| Table of Contents |
|---|
Install and run Apache Web Server
If you are not already installed the Apache web server, please refer to this download page to download the latest version of the Apache web server.
...
Your browser displays content related to Apache web server. If not, you may have to check the error logs of the Apache web server and resolve issues.
Publish files on Apache Server
Please refer the Apache documentation to locate the "web site publish directory" of the Apache server.
...
The above links display the content of the TAD XML files in the browser.
Editing the hosts file
Hosts file is a text file that contains entries to map host names to IP addresses. By editing this file it is possible to redirect requests (by the WSO2 Governance Registry) requesting ws-i.org site resources to out locally hosted Apache web server resources. In Linux environment, the hosts file is located at:
...
| Info |
|---|
It is always best to take a backup of the host file before modifying it. In this page we assume that Apache web server and WSO2 Governance Registry is installed on the same machine. However, if required, you can install Apache web server on another machine with appropriate changes to the host file (which is in the machine which runs the WSO2 Governance Registry). You can point to the Apache web server machine using the host file. |
Verifying the steps
To verify these steps, locate the following link on your browser (on the machine which is not having an internet connection),
...