i think most of the soap servers offer web services in both wsdl and non-wsdl mode (like Amazon does) for a client to make request. we know in wsdl mode client has to download the wsdl file to determine how to make a request for the service. but in non-wsdl mode, how the client learns to make a request for the service?
In non-wsdl mode the client cannot learn how to utilize the remote soap server. This is up to you as developer. You will have to make sure that your client delivers what the server expects - especially parameter and response types have to have the correct types and formats.
An WSDL document describes a web service. It specifies the location of the service, and the methods of the service, using these major elements: Element. Description. <types>
The WSDL Generator component is not essential for using SOAP. Administrators can still write service calls to Content Server in SOAP if needed. The WSDL Generator provides flexibility in altering existing client applications.
A WSDL document is used to describe a web service. This description is required, so that client applications are able to understand what the web service actually does. The methods which are exposed by the web service.
In non-wsdl mode the client cannot learn how to utilize the remote soap server. This is up to you as developer. You will have to make sure that your client delivers what the server expects - especially parameter and response types have to have the correct types and formats.
In wsdl mode your client (i. e. Zend Soap Client) knowns which soap actions exist, how complex types etc. are defined and what responses are expected.
Personally I advice never to use non-wsdl mode, as there is imho no reason to do so.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With