|
|
|
|
|
- Overview
- Importing a web service into a project
- Import
- "Project explorer" pane: viewing a web service
- Description and properties of a web service
- Updating the description of a web service
- Properties of a web service modifiable in the editor
- Using a web service
- Principle
- How to set values in the HTTP header of a SOAP web service call?
- Asynchronous web service call
- Properties associated with the web service
- Properties available on the types of variables
- Advanced operations of the XML stream of the web service
- Special case: the web service returns a result whose type is not recognized by WINDEV, WEBDEV and WINDEV Mobile
- Distributing a WINDEV application that uses a web service
Importing/Consuming web services
WINDEV, WEBDEV and WINDEV Mobile allow you to directly import web services into your applications. A web service is a set of entry points made available to users in order to perform different processes. For example, a remote access service provides the processes used to access the data. Data exchange with a web service is done in XML format, via SOAP (Simple Object Access Protocol) and HTTP. From the description in WSDL format (Web Services Description Language) of this service, WINDEV, WEBDEV or WINDEV Mobile will automatically generate the WLanguage types and functions corresponding to the programming interface of web service. To use the web service, simply use the functions generated during the import. This help page presents: Importing a web service into a project Import To import a web service: - On the "Project" tab, in the "Project" group, expand "Import" and select "A web service".
The web service import wizard starts.
- In the wizard, the presentation screen is displayed. Go to the next step.
- Specify the location of the WSDL. This file corresponds to the web service description. It contains the description of each function found in the web service as well as their parameters. Two methods can be used to locate the WSDL:
- from a URL, HTTP address where the WSDL is found.
Remarks: - You have the ability to specify the username and the password if an authentication is required.
- The "Proxy" button is used to configure the proxy options if necessary.
- from an XML file found on the current computer.
- Finish the wizard. A message is displayed, indicating that the import is ended.
- The Web service is automatically added to the "Project Explorer" pane (in the "Imported Webservices" branch).. It is ready to use.
"Project explorer" pane: viewing a web service The imported Web service is displayed in the "Project Explorer" pane, "Imported Webservices" folder.: The structure includes: - the name of the web service.
- the name of each function.
- the name of a structure containing either the call parameters, or the return values.
- the name of each variable in the structure.
Description and properties of a web service Updating the description of a web service As a web service evolves (fixes, new versions, etc.), its description may also evolve. To update the description of a web service in your project: - Select the web service in the "Project explorer" pane.
- Select "Update" from the popup menu.
Remark: Web services imported using legacy mode cannot be updated. Properties of a web service modifiable in the editor To modify the properties of a web service in the editor: - Select the web service in the "Project explorer" pane.
- Select "Description" in the context menu.
- The window of properties is displayed. The following properties can be modified in this window:
- The import address of web service: it is the URL to the WSDL describing the web service.
- The username and the password used to import the WSDL.
Principle To use a web service: - Declare 2 variables: a variable used to specify the call parameters and a variable used to retrieve the response.
- Initialize each variable of the call structure.
Important: the order of assignment of variables is used in the XML generated in the SOAP request. It is therefore necessary to assign the variables in the order specified in the documentation of the web service function. - Call the web service function by passing the call variable as parameter and retrieve the response variable in return.
Example: trackingSearch is trackSearch
trackingSearchRes is resultTrackSearch
trackingSearch.accountNumber = 99999999
trackingSearch.consigneesCountry = "FR"
trackingSearch.consigneesZipCode = "37100"
trackingSearch.sendersRef = "111111"
trackingSearchRes = TrackingServiceWSService.trackSearch(trackingSearch)
IF ErrorOccurred() THEN
Trace("Echec de l'appel au service Web : " + ErrorInfo(errFullDetails))
ELSE
Trace("Webservice correctement exécuté")
END
In most cases, the result returned by the web service is in XML format. Therefore, the XML functions must be used to decode the response. How to set values in the HTTP header of a SOAP web service call? To set values in the HTTP header of a SOAP web service call: - Declare a wsRequest variable.
- Use the HTTPHeader property to set the header values.
- Call the web service procedure by specifying the name of the wsRequest variable as the first parameter.
Example:
C is wsRequest
C.HTTPHeader["key"] = "Value"
WebServiceProc(C, param1_WS, param2_WS)
Trace(C.XMLSource)
Asynchronous web service call In some cases, the call to a web service may take too long. It may be necessary to make an asynchronous call to the web service, using the following syntax: APRES <Résultat> = <Procédure d'appel au Webservice> FAIRE <Code exécuté uniquement lorsque le Webservice aura été exécuté et aura envoyé la réponse> FIN <Code exécuté directement après l'appel du Webservice> Using this syntax, you can prevent the call to the web service from blocking the application. The program continues to run even if the web service has not yet responded. The previous example becomes:
trackingSearch is trackSearch
trackingSearchRes is resultTrackSearch
trackingSearch.accountNumber = 99999999
trackingSearch.consigneesCountry = "FR"
trackingSearch.consigneesZipCode = "37100"
trackingSearch.sendersRef = "111111"
APRES trackingSearchRes = TrackingServiceWSService.trackSearch(trackingSearch) DO
IF ErrorOccurred() THEN
Trace("Echec de l'appel au service Web: " + ErrorInfo(errFullDetails))
ELSE
Trace("Webservice correctement exécuté")
END
END
For more details, see AFTER statement. Properties associated with the web service To handle a web service programmatically, simply use its name (as it appears in the "Project explorer" pane). Remark: You can drag and drop directly from the "Project explorer" pane to the code editor to insert the name of the web service. The following properties can be modified through programming: | | | nom | Type used | Effect |
---|
Address | Character string | Used to replace the call address of web service described in the WSDL by another URL. This property is useful if the web service is hosted on different servers. This property has the following format: "http://server:port/webservice_path". For a web service generated with WINDEV and deployed on a WEBDEV Application Server, it is the URL of the "awws" file. Remarks: - The modification of this property replaces all the URLs described in the WSDL.
- If this property corresponds to an empty string (""), the URLs described in the WSDL will be re-used.
| | Integer constant | Used to force the HTTP authentication method: - auAutomatic (default value): automatic authentication method.
- auBasic: Basic authentication method.
- auNegotiate: Negotiate authentication method.
Caution: This authentication method is not supported by Linux executables.
| IgnoreError | Combination of constants | Used to ignore the certificate errors. the following constants can be used:- httpIgnoreInvalidCertificate: Used to ignore an invalid certificate or a certificate coming from an unknown company.
- httpIgnoreInvalidCertificateName: Used to ignore the name of the site found in the certificate.
- httpIgnoreExpiredCertificate: Used to ignore the date of the certificate.
- httpIgnoreRedirectToHTTP: Used to redirect to a non-secure server.
- httpIgnoreRedirectToHTTPS: Used to redirect to a secure server.
- httpIgnoreRevocation: Used to ignore the check in the list of revoked certificates.
Remarks: - Only the following errors are supported: httpIgnoreExpiredCertificate, httpIgnoreInvalidCertificate, httpIgnoreInvalidCertificateName, httpIgnoreRevocation. The other errors are ignored. For backward compatibility, all the errors are ignored by default.
| MethodHTTP | Integer constant | HTTP method used to call the web service:- httpPost (default value): POST method
- httpPut: PUT method
| Password | Character string | Password used for authentication in the HTTP requests sent to the web service. This name is used only if authentication is required to access the server where the web service is hosted. | Port | Character string | Name of the port defined in the WSDL. It is the port used to communicate with the server that hosts the web service. Contact your network manager or the owner of the web service. | User | Character string | Username used for authentication in the HTTP requests sent to the web service. This name is used only if authentication is required to access the server where the web service is hosted. With the Negotiate authentication method, the domain must be added to the user depending on the configuration: monWebservice..Utilisateur = "DOMAINE\Utilisateur" or monWebservice..Utilisateur = "Utilisateur@DOMAINE" | VersionHTTP | Integer constant | HTTP version used by the server: - httpVersion2: HTTP version 2.0. If the server does not support this version, an older version is used.
- httpVersion2Only: Forces HTTP version 2.0: if the server does not support this version, a fatal error is displayed.
- httpVersion1_1: HTTP version 1.1.
- httpVersion1_0: HTTP version 1.0.
- httpVersionDefault: HTTP version 1.0.
| Remark: - If a username and a password are specified, the authentication of the HTTP requests will be done by using the "Basic" authentication schema, in which the parameters are in readable format in the HTTP request. We recommend that you use HTTPS requests if the authentication is required.
- If the server that hosts the web service requires a Windows authentication in HTTP, HTTPConfigure must be called before consuming the web service (in order to use Internet Explorer for the HTTP requests).
- The maximum timeout can be specified with HTTPTimeOut.
Caution: The properties modifiable in the editor and the properties modifiable through programming have no link. Properties available on the types of variables The types of variables automatically declared when importing the WSDL propose several properties: | | | nom | Type used | Effect |
---|
Exist | Boolean | - True if the type of variable exists in the web service response,
- False otherwise.
| Occurrence | entier | Number of elements of this type in the web service response. A web service can return arrays of variables. The Count property allows you to get the size of the returned array and the [ ] operator allows you to access the elements of the array. | Type | Character string | Name of the variable type. This property is used when a web service is likely to return responses of different types. | Value | Variant | Value of the variable. Remark: This property is accessed by default when only the variable name is used. For example:
monWebservice.VariableRequete = SAI_Valeur
is equivalent to:
monWebservice.VariableRequete..Value = SAI_Valeur
|
Advanced operations of the XML stream of the web service In some cases, you may have to handle the XML data stream exchanged with the web service. For example, some web services require adding headers to their XML stream to enable authentication, or return metadata in the response headers. The following functions can be used to respond to these particular requests: | | SOAPAddAttribute | Declares the additional attributes (not found in the WSDL) on a web service variable automatically generated. It is used in advanced programming when the WSDL returned by the web service does not match the expected type. | SOAPAddHeader | Adds custom headers into a call to a web service. | SOAPGetHeader | Reads the information contained in the header of a web service response. | SOAPPrepare | Builds the web service request for a given function and parameters, but does not send it. |
Special case: the web service returns a result whose type is not recognized by WINDEV, WEBDEV and WINDEV Mobile The types of variables available in WINDEV and in a SOAP web service can be different. Simple types (boolean, integer, etc.) and complex types (datetime, duration, structures, arrays of simple types and array of structures, nested structures, etc.) used in the web service are automatically converted to WLanguage and vice versa, when the service is imported into a project. The Array types are also supported. The most evolved types (classes, advanced types of WLanguage, etc.) are processed as character strings in the WLanguage code. These strings contain the XML code corresponding to the type of variable returned by the web service and its contents. Therefore, if a web service returns a result as a class instance, this result will be processed in the procedure as a character string in XML format. Then, you will have to process this character string (in WLanguage) in order to extract the desired information. For more details, see the XML functions. Remarks: - If the web service returns a structure, the names of the members of the return structure are case-sensitive.
- If you are using a structure as parameter of a web service function and if a DATE member is not assigned, the following error will be displayed: "The 0000-00-00 value does not respect the XSD schema".
Distributing a WINDEV application that uses a web service To distribute an application that uses a web service, simply include the file that describes the web service (.wsdl file) in the library of the application. For the application to run the web service, the end-user computer must be connected to the Internet. Remark: Before distributing an application that uses a web service, it is recommended to check the license and the distribution rights of this service (in case there is a free for the service).
Related Examples:
|
Training (WINDEV): WD Webservice Client
[ + ] This example illustrates the use of WebServices. It explains how to retrieve, from a WebService, images according to keywords. This project is the client that connects to the "WD Webservice Server" WebService.
|
|
Training (WINDEV): WD Webservice Server
[ + ] This example illustrates the use of the WebServices. It explains how to create a WebService by providing some images according to keywords. This project is the WebService that is used th the WD Webservice Client project.
|
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|