WebService WSDL file tags explained __web

<?xml version= "1.0" encoding= "UTF8"?> <wsdl:definitions targetnamespace= "http://www.57market.com.cn/ HelloService "xmlns:soapenc12=" http://www.w3.org/2003/05/soapencoding "xmlns:tns=" http://www.57market.com.cn/ HelloService "xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/"xmlns:xsd=" Http://www.w3.org/2001/XMLSchema "xmlns: soap11= "http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdlsoap= "http://schemas.xmlsoap.org/wsdl/soap/" xmlns:
	soapenc11= "http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12= "Http://www.w3.org/2003/05/soapenvelope" >
	 <!--* Type element, which defines the data format for exchanging information.
	 * To achieve maximum interoperability (interoperability) and platform neutrality (neutrality), the WSDL uses XML Schema datatypes * abbreviated XSD as the standard type system and uses it as the intrinsic type system. * Below is the data definition section, which defines two elements, one is SayHello, and the other is sayhelloresponse: * SayHello: Defines a complex type that contains only a simple string that will be used to describe the input part of the operation in the future; Sayhelloresponse: Defines a complex type that contains only a simple string that will be used to describe the return value of the operation in the future;-<wsdl:types> <xsd:schema xmlns:xsd= "htt P://www.w3.org/2001/xmlschema "Attributeformdefault= "qualified" elementformdefault= "qualified" targetnamespace= "Http://www.57market.com.cn/HelloService" >
                        <xsd:element name= "SayHello" > <xsd:complexType> <xsd:sequence>
                    <xsd:element maxoccurs= "1" minoccurs= "1" name= "In0" nillable= "true" type= "xsd:string"/>
            </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name= "Sayhelloresponse" > <xsd:complexType> <xsd:sequence&
                        Gt <xsd:element maxoccurs= "1" minoccurs= "1" name= "Out" nillable= "true" type= "xsd:string"/> </xs d:sequence> </xsd:complexType> </xsd:element> </xsd:schema> & Lt;/wsdl:types> <!--* The message element specifies the various parts of the message that the XML data type consists of.
	The message element is used to define the input and output parameters of the operation. * This section is an abstract definition of the information format: two messages defined SayhelloreSponse and Sayhellorequest: * The request message format of the Sayhellorequest:sayhello operation, consisting of a message fragment with the name parameters, the element is the element in the types we defined earlier; The response message format of the Sayhelloresponse:sayhello operation consists of a message fragment with the name parameters, and the element is the element in the types that we have previously defined *; * If RPC-style message delivery is used,
	You only need to modify the element elements in the document to type. * Message: The structure used to define the message * Part: Specify the label section defined in reference types--<wsdl:message name= "Sayhellorequest" > <wsdl:par T name= "parameters" element= "Tns:sayhello"/> </wsdl:message> <wsdl:message name= "Sayhelloresponse"
        ; <wsdl:part name= "Parameters" element= "Tns:sayhelloresponse"/> </wsdl:message> <!--* porttype element defined W Operation of the EB service.
	An operation defines an XML message that can appear in the input and output data streams. * A collection of some abstract operations.
	Each operation is associated with an input message and an output message. * PortType defines the type of invocation pattern for the service, which contains an operation SayHello method, which contains input and output indicating that * The operation is a request/response pattern, the request message is the Sayhellorequest defined earlier, * The response message is the previously defined sayhelloresponse.
	Input represents the payload that is passed to the Web service, * Output: The message represents the payload that is passed to the customer. * PortType: Use to define the SEI * operation on the server: Use to specify the method of application in the SEI * Input: Specifies the data transmitted by the Client app, referring to the above and defined <message> * output: Specify the service side to return to the guestThe user's data will refer to the above and defined <message> <wsdl:porttype name= "Helloserviceporttype" > <wsdl:operation n Ame= "SayHello" > <wsdl:input name= "sayhellorequest" message= "Tns:sayhellorequest"/> <w Sdl:output name= "Sayhelloresponse" message= "Tns:sayhelloresponse"/> </wsdl:operation> </wsdl:port
	type> <!--* Binding elements describe the protocols, data formats, security, and other properties of a particular service interface.
	* Specify the actual protocol and data format specification for messages used in operations and porttype.
	* Binding: Used to define the implementation class of the SEI * Type property: Reference above <portType> * <soap:operation style= "document"/> Bound data is a document (XML) * Operation: Use to define the method of implementation * <soap:operation style= "document"/> Transfer is document (XML) * Input: Specify the data sent by the client app * <soap:bo  Dy use= "literal"/&GT;: Text data * Output: Specify server-side data returned to client * <soap:body use= "literal"/&GT;: Text data--<wsdl:binding Name= "helloservicehttpbinding" type= "Tns:helloserviceporttype" > <wsdlsoap:binding style= "Document" Transpor
    t= "Http://schemas.xmlsoap.org/soap/http"/>    <wsdl:operation name= "SayHello" > <wsdlsoap:operation soapaction= ""/> <wsdl:inp
            UT name= "sayhellorequest" > <wsdlsoap:body use= "literal"/> </wsdl:input> <wsdl:output name= "Sayhelloresponse" > <wsdlsoap:body use= "literal"/> </w Sdl:output> </wsdl:operation> </wsdl:binding> <!--* Service element. The service element contains a set of port elements.
	The Port associates the endpoint with the binding element defined by the service interface.
	* Port Specifies a binding address, which defines a terminal for communication. * Service: A WebService Container * Name: property: It is used to specify the portal of a server-side processing request (which is the implementation of the SEI) * Binding properties: Refer to the <binding> address defined above: Current WebService request Address--<wsdl:service name= "HelloService" > <wsdl:port name= "helloservicehttpport" b inding= "tns:helloservicehttpbinding" > <soap:address location= "Http://localhost:8080/xfire/services/Hello Service "/> </wsdl:port> </wsdl:service> </wsdl:definitions>