Back Forward dotNET Connector rules
Understanding the WSDL tab
  1. About 
  2. New 
  3. Service 
  4. Request 
  5. Response 
  6. Faults 
  1. Advanced 
  2. WSDL 
  3. History 

When you use the Accelerator to generate the connector, the Accelerator stores the contents of the Web service’s WSDL file on the WSDL tab of the connector. This information is read-only.

Having the WSDL stored in the rule enables you to move the connector with the rest of your application when you migrate an application from a development system to a production system. When the Connector Accelerator generates a SOAP or dotNET connector, it also generates Java classes needed by the Axis client (Axis stub classes) embedded in PRPC. However, the Java classes aren’t included when you export rules. Because the WSDL tab holds the original WSDL file, the connector can re-generate the Axis stub classes if it runs and discovers that those classes are not present. This means that you can develop your connectors on a development system and then move them to a production system. You do not need to use the Connector Accelerator to generate them twice (development and production).

The data on this tab includes the top-level document only. It does not include any related (or included) WSDL or XSD files. If the connector needs to re-generate the Axis stub classes from the WSDL on this tab and it discovers a referenced file, it uses the URL of that file to locate it on the Web. If the file has a relative URL, the connector uses the URL specified in the WSDL URL field on this tab to determine the absolute URL for the referenced file.

This tab contains a single field WSDL URL. If the WSDL references files with relative URLs and the URL of the original WSDL file changed after you generated the rule, carefully edit the value in this field so that it is correct. Otherwise do not edit this field.

Up About Connect dotNET rules