Entering content frame

Function documentation Loading WSDL Definitions Locate the document in its SAP Library structure

Use

The WSDL location is parsed and loaded in internal structures called WSDL definitions. If mirror representation of a remote location is used (this is obtained from the com.sap.engine.services.webservices.wsdl.ImportTool located in webservices_lib library), location mapping option must be passed in the generator configuration. This is a Hashtableproperty in the ProxyGeneratorConfig and must be set with the following method:

public void setLocationMap(Hashtable locationMap)

Here is a simple location map created by the WSDL import tool, mapping absolute locations to local locations of downloaded WSDLs.

[http://localhost/testWS/cfg1?wsdl] = [wsdlroot.wsdl]

[http://localhost/testWS/cfg1/porttypes?wsdl&style=rpc] = [wsdlfile2.wsdl]

[http://localhost/testWS/cfg1/porttypes?wsdl&style=document] = [wsdlfile4.wsdl]

[http://localhost/testWS/cfg1/bindings?wsdl&style=rpc] = [wsdlfile1.wsdl]

[http://localhost/testWS/cfg1/bindings?wsdl&style=document] = [wsdlfile3.wsdl]

[] = [http://localhost/testWS/cfg1?wsdl]

The root of the downloaded WSDL is [http://localhost/testWS/cfg1?wsdl]. This location map is then used and the WSDL location [wsdlroot.wsdl] is passed. The import tool is a class com.sap.engine.services.Webservices.wsdl.WSDLImportTool that can download WSDLs from remote to local locations including the import structure. The files remain untouched but it creates a location map that maps the remote absolute locations to a local relative, so that this map together with the local root as a WSDL location can be passed to the proxy generator later on. This is necessary because remote locations cannot be used when deploying Web services clients. Typically the visual tools make these steps so that users do not use this option in most cases.

 

Leaving content frame