This binding specifies that messages are sent using the document/literal message style. Adding Headers to a SOAP 1.2 Message Overview. SOAP message headers are defined by adding wsoap12:header elements to your SOAP 1.2 message. The wsoap12:header element is an optional child of the input, output, and fault elements of the binding. The header becomes part of the parent message.
Appendix D
Interface Description of a Web Service in the SAP Web AS
<?xml version='1.0' encoding='UTF-8' ?>
<definitions xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:s0='urn:sap-com:document:sap:rfc:functions' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:http='http://schemas.xmlsoap.org/wsdl/http/' targetNamespace='urn:sap-com:document:sap:rfc:functions'>
<types>
<xsd:schema targetNamespace='urn:sap-com:document:sap:rfc:functions'>
<xsd:element name='STFC_CONNECTION'>
<xsd:complexType>
<xsd:sequence>
<xsd:element name='REQUTEXT'>
<xsd:simpleType>
<xsd:restriction base='xsd:string'>
<xsd:length value='255' />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='STFC_CONNECTION.Response'>
<xsd:complexType>
<xsd:sequence>
<xsd:element name='ECHOTEXT'>
<xsd:simpleType>
<xsd:restriction base='xsd:string'>
<xsd:length value='255' />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name='RESPTEXT'>
<xsd:simpleType>
<xsd:restriction base='xsd:string'>
<xsd:length value='255' />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
<message name='STFC_CONNECTIONInput'>
<part name='parameters' element='s0:STFC_CONNECTION' />
</message>
<message name='STFC_CONNECTIONOutput'>
<part name='parameters' element='s0:STFC_CONNECTION.Response' />
</message>
<portType name='STFC_CONNECTIONPortType'>
<operation name='STFC_CONNECTION'>
![Http Http](/uploads/1/2/5/6/125603676/378904459.jpg)
<input message='s0:STFC_CONNECTIONInput' />
<output message='s0:STFC_CONNECTIONOutput' />
</operation>
</portType>
<binding name='STFC_CONNECTIONBinding' type='s0:STFC_CONNECTIONPortType'>
<soap:binding transport='http://schemas.xmlsoap.org/soap/http' />
<operation name='STFC_CONNECTION'>
<soap:operation soapAction='http://www.sap.com/STFC_CONNECTION' />
<input>
<soap:body use='literal' />
</input>
<output>
<soap:body use='literal' />
</output>
</operation>
</binding>
<service name='STFC_CONNECTIONService'>
<documentation>SAP Service STFC_CONNECTION via SOAP</documentation>
<port name='STFC_CONNECTIONPortType' binding='s0:STFC_CONNECTIONBinding'>
<soap:address location='http://binmain:8080/sap/bc/soap/rfc' />
</port>
</service>
</definitions>
Hi all,
I'm using this package to create a SOAP service but the customer required me to generate a SOAP 1.2 WSDL (because they have a tool that sends SOAP requests only with this format).
I've used the following code in order to generate it (taken from one of your tests):
I've used the following code in order to generate it (taken from one of your tests):
But he said that this is not good because the soap namespace of the WSDL is still at 1.1 version. It should be
http://schemas.xmlsoap.org/wsdl/soap12/
instead it's http://schemas.xmlsoap.org/wsdl/soap/
Looking at the code it seems that the soap namespace is not dependent on the binding, it's always a SOAP 1.1 namespace regardless of the binding used.
Is it a bug?
I've also tried to do a test client using the Add Web Reference Wizard and, when calling the methods i got the following error:
ArgumentException: The envelope version of the incoming message (Soap11 (http://schemas.xmlsoap.org/soap/envelope/)) does not match that of the encoder (Soap12 (http://www.w3.org/2003/05/soap-envelope)). Make sure the binding is configured with the same version as the expected messages.