WSDL Accessor
Zend_Soap_Wsdl constructorZend_Soap_Wsdl constructor takes three parameters:
addMessage() methodaddMessage($name, $parts) method adds new message description to the WSDL document (/definitions/message element). Each message correspond to methods in terms of Zend_Soap_Server and Zend_Soap_Client functionality. $name parameter represents message name. $parts parameter is an array of message parts which describe SOAP call parameters. It's an associative array: 'part name' (SOAP call parameter name) => 'part type'. Type mapping management is performed using addTypes(), addTypes() and addComplexType() methods (see below).
addPortType() methodaddPortType($name) method adds new port type to the WSDL document (/definitions/portType) with the specified port type name. It joins a set of Web Service methods defined in terms of Zend_Soap_Server implementation. See http://www.w3.org/TR/wsdl#_porttypes for the details. addPortOperation() methodaddPortOperation($portType, $name, $input = false, $output = false, $fault = false) method adds new port operation to the specified port type of the WSDL document (/definitions/portType/operation). Each port operation corresponds to a class method (if Web Service is based on a class) or function (if Web Service is based on a set of methods) in terms of Zend_Soap_Server implementation. It also adds corresponding port operation messages depending on specified $input, $output and $fault parameters.
See http://www.w3.org/TR/wsdl#_request-response for the details. addBinding() methodaddBinding($name, $portType) method adds new binding to the WSDL document (/definitions/binding). 'binding' WSDL document node defines message format and protocol details for operations and messages defined by a particular portType (see http://www.w3.org/TR/wsdl#_bindings). The method creates binding node and returns it. Then it may be used to fill with actual data.
Zend_Soap_Server implementation uses
addBindingOperation() methodaddBindingOperation($binding, $name, $input = false, $output = false, $fault = false) method adds an operation to a binding element (/definitions/binding/operation) with the specified name.
It takes Zend_Soap_Server implementation adds corresponding binding entry for each Web Service method with input and output entries defining 'soap:body' element as '<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> See http://www.w3.org/TR/wsdl#_bindings for the details. addSoapBinding() methodaddSoapBinding($binding, $style = 'document', $transport = 'http://schemas.xmlsoap.org/soap/http') method adds SOAP binding ('soap:binding') entry to the binding element (which is already linked to some port type) with the specified style and transport (Zend_Soap_Server implementation uses RPC style over HTTP). '/definitions/binding/soap:binding' element is used to signify that the binding is bound to the SOAP protocol format. See http://www.w3.org/TR/wsdl#_bindings for the details. addSoapOperation() methodaddSoapOperation($binding, $soap_action) method adds SOAP operation ('soap:operation') entry to the binding element with the specified action. 'style' attribute of the 'soap:operation' element is not used since programming model (RPC-oriented or document-oriented) may be using addSoapBinding() method 'soapAction' attribute of '/definitions/binding/soap:operation' element specifies the value of the SOAPAction header for this operation. This attribute is required for SOAP over HTTP and must not be specified for other transports.
Zend_Soap_Server implementation uses
See http://www.w3.org/TR/wsdl#_soap:operation for the details. addService() methodaddService($name, $port_name, $binding, $location) method adds '/definitions/service' element to the WSDL document with the specified Wed Service name, port name, binding, and location. WSDL 1.1 allows to have several port types (sets of operations) per service. This ability is not used by Zend_Soap_Server implementation and not supported by Zend_Soap_Wsdl class. Zend_Soap_Server implementation uses:
See http://www.w3.org/TR/wsdl#_services for the details. Type mappingZend_Soap WSDL accessor implementation uses the following type mapping between PHP and SOAP types:
xsd: is "http://www.w3.org/2001/XMLSchema" namespace,
soap-enc: is a "http://schemas.xmlsoap.org/soap/encoding/" namespace,
tns: is a "target namespace" for a service.
Retrieving type informationgetType($type) method may be used to get mapping for a specified PHP type:
Adding complex type informationaddComplexType($type) method is used to add complex types (PHP classes) to a WSDL document. It's automatically used by getType() method to add corresponding complex types of method parameters or return types. Its detection and building algorithm is based on the currently active detection strategy for complex types. You can set the detection strategy either by specifying the class name as string or instance of a Zend_Soap_Wsdl_Strategy_Interface implementation as the third parameter of the constructor or using the setComplexTypeStrategy($strategy) function of Zend_Soap_Wsdl. The following detection strategies currently exist:
addComplexType() method creates '/definitions/types/xsd:schema/xsd:complexType' element for each described complex type with name of the specified PHP class. Class property MUST have docblock section with the described PHP type to have property included into WSDL description. addComplexType() checks if type is already described within types section of the WSDL document. It prevents duplications if this method is called two or more times and recursion in the types definition section. See http://www.w3.org/TR/wsdl#_types for the details. addDocumentation() methodaddDocumentation($input_node, $documentation) method adds human readable documentation using optional 'wsdl:document' element. '/definitions/binding/soap:binding' element is used to signify that the binding is bound to the SOAP protocol format. See http://www.w3.org/TR/wsdl#_documentation for the details. Get finalized WSDL documenttoXML(), toDomDocument() and dump($filename = false) methods may be used to get WSDL document as an XML, DOM structure or a file. [1] is defined as script
().
[3]
By default will be created
with the
class as detection algorithm for complex types. The first parameter
of the AutoDiscover constructor takes any complex type strategy
implementing
or a string
with the name of the class. For backwards compatibility with
boolean variables are parsed
the following way: If TRUE,
,
if FALSE.
|