edmiRemoteGetWSDL

EdmiError edmiRemoteGetWSDL(SdaiServerContext serverContextId,
                             SdaiString        repositoryName, 
                             SdaiString        modelName, 
                             SdaiString        methodType, 
                             SdaiString        schemaName, 
                             SdaiString        methodSchemaName, 
                             SdaiString        serverAddress, 
                             SdaiOptions       options 
                             SdaiOutputStream  wsdlDocument, 
                             SdaiInvocationId  *edmiInvocationId);

Generates a Web Service Definition Language (WSDL) document for the specified method schema.  The generated WSDL document contains a method signature for every function in the method schema. In WSDL terminology the query/map schema becomes a web service and the functions in the schema becomes operations. Below is an example of the service definition part of a WSDL document:
 
<wsdl:service name="ifd_wsdl_expressService">
<wsdl:port binding="impl:EDMWSSoapBinding" name="EDMWS"> 
<wsdlsoap:address location="http://localhost/EDMWS/earlybinding/DataRepository/IFD/QEX/ifd_wsdl_express"/> 
</wsdl:port> 
</wsdl:service>
 
In this example edmiRemoteGetWSDL is called with repositoryName = "DataRepository", modelName = "IFD", methodType = "QEX", methodSchemaName = "ifd_wsdl_express" and serverAddress ="http://localhost". One can observe that the name of the web service becomes method name + "Service" and repository and model is a part of the URL in the location attribute of the wsdlsoap:address tag. This URL should web service clients use when connecting to this web service. Which data model in the EDM database an operation defined here shall act upon is defined by the two sub strings following "EDMWS/earlybinding".
In addition to define the operations of the web service, all the data structures needed for input parameters and the return values are defined by XML Schema definitions. EDMwebServices support both rpc/encoded and document/literal style. The main difference between rpc/encoded and document/literal style is that rpc/encoded style support multiple reference to instances while document/literal does not.

Arguments

Return Value

Options

Example

 /* Context parameter for stream read / write. */
 typedef struct _tFileStreamContext
 {
 FILE *fp; 
 } tFileStreamContext;
  
  
 long outputFileWriter(SdaiStreamContext sc,
 char *buffer, 
 int nBytes) 
 {
 int nWritten; 
 FILE stream = ((tFileStreamContext)sc)->fp; 
  
 if (stream) { 
 if (nBytes <= 0) nBytes = strlen(buffer); 
 nWritten = fwrite(buffer, 1, nBytes, stream); 
 } 
 return (nWritten == nBytes) ? OK : -1; 
 }
  
 tSdaiOutputStream wsdlDocument;
 tFileStreamContext outContext;
  
 /* open the wsdl document file */
 outContext.fp = fopen("ifd.wsdl", "wb");
 /* Initiate the stream write descriptor wsdlDocument */
 wsdlDocument.write = &outputFileWriter;
 wsdlDocument.context = (SdaiStreamContext)&outContext;
  
 rstat = edmiRemoteGetWSDL(serverContextId
 "DataRepository", 
 "IFD", 
 "QEX", 
 "", 
 "ifd_wsdl_express", 
 "http://localhost", 
 0, 
 &wsdlDocument, 
 NULL); 
 if (rstat) {
 /* handle the error */ 
 }
 fclose(outContext.fp);
 . . .

See also

Related functions: edmiRemoteExecuteWebService, edmiRemoteExecuteWebServiceEx