WSDL 1.1 Binding Extension for SOAP 1.2

Hi,
The WSDL file that is generated in XI 3.0 uses the specification SOAP 1.1
To apply the specification "WSDL 1.1 Binding Extension for SOAP 1.2", is it sufficient with adding the necessary parameters or have I to create the WSDL file again?
Parameters:
<wsdl:definitions
   targetNamespace="http://example.com"
   xmlns:tns="http://example.com"
   xmlns:wsoap12="http://schemas.xmlsoap.org/wsdl/soap12/"
   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
   xmlns:xs="http://www.w3.org/2001/XMLSchema">
If I have to create it again, which editor/utility can I use to create it?
Have I to activate some checkbox in the communication channel (Receiver Agreement/Sender Agreement) to this works?
kind regards,
Samantha.

Hi Samantha
I believe that this is applicable in XI 3,0 from SP 20.
king regards

Similar Messages

How to write won WSDL file for SOAP adapter ?

Hi experts
Can any one expalin me how to write WSDL file for SOAP adapter ?
What and all things i need to know ? i have no idea on this....
I got the business but to WSDL ...i am very new to this
Adv...thanks
Rakesh

HI,
Please see the below links,
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a61ff
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
/people/kevin.liu/blog/2006/04/12/wsdl-11-binding-extension-for-soap-12
Regards
Chilla..

Could not find binding output for operation getMessage

Hi,
I am getting a error while involking a service which is implemented using Axis2.
The error is "[email protected]1 : Could not find binding output for operation getMessage".
Please help me in solving the problem. The WSDL of the service looks like this...
<wsdl:definitions xmlns:axis2="http://ws.fs.com" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns0="http://ws.fs.com/xsd" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://ws.fs.com">
<wsdl:documentation>GetMessageService</wsdl:documentation><wsdl:types><xs:schema xmlns:ns="http://ws.fs.com/xsd" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://ws.fs.com/xsd">
<xs:element name="getMessage">
<xs:complexType>
<xs:sequence>
<xs:element name="param0" nillable="true" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="getMessageResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="return" nillable="true" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema></wsdl:types><wsdl:message name="getMessageMessage"><wsdl:part name="part1" element="ns0:getMessage" /></wsdl:message><wsdl:message name="getMessageResponse"><wsdl:part name="part1" element="ns0:getMessageResponse" /></wsdl:message><wsdl:portType name="GetMessageServicePortType"><wsdl:operation name="getMessage"><wsdl:input xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" message="axis2:getMessageMessage" wsaw:Action="urn:getMessage" /><wsdl:output message="axis2:getMessageResponse" /></wsdl:operation></wsdl:portType><wsdl:binding name="GetMessageServiceSOAP11Binding" type="axis2:GetMessageServicePortType"><soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="getMessage"><soap:operation soapAction="urn:getMessage" style="document" /><wsdl:input><soap:body use="literal" /></wsdl:input><wsdl:output><soap:body use="literal" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:binding name="GetMessageServiceSOAP12Binding" type="axis2:GetMessageServicePortType"><soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="getMessage"><soap12:operation soapAction="urn:getMessage" style="document" /><wsdl:input><soap12:body use="literal" /></wsdl:input><wsdl:output><soap12:body use="literal" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:binding name="GetMessageServiceHttpBinding" type="axis2:GetMessageServicePortType"><http:binding verb="POST" /><wsdl:operation name="getMessage"><http:operation location="getMessage" /><wsdl:input><mime:content type="text/xml" /></wsdl:input><wsdl:output><mime:content type="text/xml" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:service name="GetMessageService"><wsdl:port name="GetMessageServiceSOAP11port_http" binding="axis2:GetMessageServiceSOAP11Binding"><soap:address location="http://192.168.74.248:8080/axis2/services/GetMessageService" /></wsdl:port><wsdl:port name="GetMessageServiceSOAP12port_http" binding="axis2:GetMessageServiceSOAP12Binding"><soap12:address location="http://192.168.74.248:8080/axis2/services/GetMessageService" /></wsdl:port><wsdl:port name="GetMessageServiceHttpport" binding="axis2:GetMessageServiceHttpBinding"><http:address location="http://192.168.74.248:8080/axis2/services/GetMessageService" /></wsdl:port></wsdl:service></wsdl:definitions>
Thanks in advance.
Kiran

Im having the exact same problem.
Has anyone found out how to fix this? Ive removed any extra soap bindings generated by axis2 and fixed a few problems with the wsdl but to no avail.
Any ideas?
Thanks in advance,
Ian Harrigan

Could not find binding output for operation ...

Hi all !!!
I have a big problem:
[email protected]5 : Could not find binding output for operation getScore
I invoke a web service called IPODShopService from my process BPEL.
this is the WSDL:
wsdl:definitions targetNamespace="http://service.integration.ipodshop.it">
<wsdl:documentation>
          Please Type your service description here
     </wsdl:documentation>
−
     <wsdl:types>
−
     <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://service.integration.ipodshop.it/xsd">
−
     <xs:element name="getScore">
−
     <xs:complexType>
−
     <xs:sequence>
<xs:element name="nome" nillable="true" type="xs:string"/>
<xs:element name="cognome" nillable="true" type="xs:string"/>
<xs:element name="email" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
−
     <xs:element name="getScoreResponse">
−
     <xs:complexType>
−
     <xs:sequence>
<xs:element name="return" nillable="true" type="xs:int"/>
</xs:sequence>
</xs:complexType>
</xs:element>
−
     <xs:element name="CreateOrder">
−
     <xs:complexType>
−
     <xs:sequence>
<xs:element name="nome" nillable="true" type="xs:string"/>
<xs:element name="cognome" nillable="true" type="xs:string"/>
<xs:element name="email" nillable="true" type="xs:string"/>
<xs:element name="list" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
−
     <xs:element name="CreateOrderResponse">
−
     <xs:complexType>
−
     <xs:sequence>
<xs:element name="return" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
−
     <wsdl:message name="CreateOrderMessage">
<wsdl:part name="part1" element="ns0:CreateOrder"/>
</wsdl:message>
−
     <wsdl:message name="CreateOrderResponse">
<wsdl:part name="part1" element="ns0:CreateOrderResponse"/>
</wsdl:message>
−
     <wsdl:message name="getScoreMessage">
<wsdl:part name="part1" element="ns0:getScore"/>
</wsdl:message>
−
     <wsdl:message name="getScoreResponse">
<wsdl:part name="part1" element="ns0:getScoreResponse"/>
</wsdl:message>
−
     <wsdl:portType name="IPODShopServicePortType">
−
     <wsdl:operation name="CreateOrder">
<wsdl:input message="axis2:CreateOrderMessage" wsaw:Action="urn:CreateOrder"/>
<wsdl:output message="axis2:CreateOrderResponse"/>
</wsdl:operation>
−
     <wsdl:operation name="getScore">
<wsdl:input message="axis2:getScoreMessage" wsaw:Action="urn:getScore"/>
<wsdl:output message="axis2:getScoreResponse"/>
</wsdl:operation>
</wsdl:portType>
−
     <wsdl:binding name="IPODShopServiceSOAP11Binding" type="axis2:IPODShopServicePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
−
     <wsdl:operation name="CreateOrder">
<soap:operation soapAction="urn:CreateOrder" style="document"/>
−
     <wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
−
     <wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
−
     <wsdl:operation name="getScore">
<soap:operation soapAction="urn:getScore" style="document"/>
−
     <wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
−
     <wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
−
     <wsdl:binding name="IPODShopServiceSOAP12Binding" type="axis2:IPODShopServicePortType">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
−
     <wsdl:operation name="CreateOrder">
<soap12:operation soapAction="urn:CreateOrder" style="document"/>
−
     <wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
−
     <wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
−
     <wsdl:operation name="getScore">
<soap12:operation soapAction="urn:getScore" style="document"/>
−
     <wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
−
     <wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
−
     <wsdl:binding name="IPODShopServiceHttpBinding" type="axis2:IPODShopServicePortType">
<http:binding verb="POST"/>
−
     <wsdl:operation name="CreateOrder">
<http:operation location="CreateOrder"/>
−
     <wsdl:input>
<mime:content type="text/xml"/>
</wsdl:input>
−
     <wsdl:output>
<mime:content type="text/xml"/>
</wsdl:output>
</wsdl:operation>
−
     <wsdl:operation name="getScore">
<http:operation location="getScore"/>
−
     <wsdl:input>
<mime:content type="text/xml"/>
</wsdl:input>
−
     <wsdl:output>
<mime:content type="text/xml"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
−
     <wsdl:service name="IPODShopService">
−
     <wsdl:port name="IPODShopServiceSOAP11port_http" binding="axis2:IPODShopServiceSOAP11Binding">
<soap:address location="http://192.168.0.4:8083/IPODv7/services/IPODShopService"/>
</wsdl:port>
−
     <wsdl:port name="IPODShopServiceSOAP12port_http" binding="axis2:IPODShopServiceSOAP12Binding">
<soap12:address location="http://192.168.0.4:8083/IPODv7/services/IPODShopService"/>
</wsdl:port>
−
     <wsdl:port name="IPODShopServiceHttpport" binding="axis2:IPODShopServiceHttpBinding">
<http:address location="http://192.168.0.4:8083/IPODv7/services/IPODShopService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
and the bpel code:
<partnerLink name="ServiceIPOD_v6.1"
partnerRole="IPODShopServicePortType_Role"
partnerLinkType="ns31:IPODShopServicePortType_PL"/>
<invoke name="CustInfofromIPOD_v4" partnerLink="ServiceIPOD_v6.1"
portType="ns31:IPODShopServicePortType" operation="getScore"
inputVariable="CustInfofromIPOD_v1_getScore_InputVariable"
outputVariable="CustInfofromIPOD_v1_getScore_OutputVariable"/>
<definitions
targetNamespace="http://service.integration.ipodshop.it"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:axis2="http://service.integration.ipodshop.it"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
<import namespace="http://service.integration.ipodshop.it" location="http://localhost:8083/IPODv7/services/IPODShopService?wsdl"/>
<plnk:partnerLinkType name="IPODShopServicePortType_PL">
<plnk:role name="IPODShopServicePortType_Role">
<plnk:portType name="axis2:IPODShopServicePortType"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
do have you any idea?
please, help me!
thanks
Stefano

Hi,
Just in case someone runs into the same problem, I live here my solution:
In may case the problem was the wsdl definition. I developed the web service in java and generated the wsdl with Maven. Automatically it generates the wsdl like this (I just copy the last section):
<wsdl:service name="tso-ws">
<wsdl:port name="tso-wsHttpSoap11Endpoint" binding="ns:tso-wsSoap11Binding">
<soap:address location="http://localhost:8080/axis2/services/tso-ws"/>
</wsdl:port>
<wsdl:port name="tso-wsHttpSoap12Endpoint" binding="ns:tso-wsSoap12Binding">
<soap12:address location="http://localhost:8080/axis2/services/tso-ws"/>
</wsdl:port>
<wsdl:port name="tso-wsHttpEndpoint" binding="ns:tso-wsHttpBinding">
<http:address location="http://localhost:8080/axis2/services/tso-ws"/>
</wsdl:port>
</wsdl:service>
The problem was the <wsdl:service name="tso-ws"> section. There were 3 port definitions with 3 different bindings but all of them have the same service location. So In the BPEL process I created the partner link using the service location.
I guess BPEL was using the http binding, so I deleted two of the por definitions and just left this in the <wsdl:service name="tso-ws"> section of the wsdl
<wsdl:service name="tso-ws">
<wsdl:port name="tso-wsHttpSoap12Endpoint" binding="ns:tso-wsSoap12Binding">
<soap12:address location="http://localhost:8080/axis2/services/tso-ws"/>
</wsdl:port>
By doing this, it works. I read in some forums that BPEL doesn't work with the http_post protocol so that's why I deleted that definition. And someone told me that it uses soap12 so that's why I deleted that definition also.
That's the way I solved it. Hope this helps.
Regards,
Zaloa

Unable to find a WSDL that has a definition for service

Dear all
I have a very simple composite applicationexposing a web service. When I deploy the application I get:
There was an error deploying the composite on soa_server1: Deployment Failed: Unable to find a WSDL that has a definition for service {http://soa/sf/login}bpelprocess1_client_ep and port loginPort_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.
However the build process shows no errors. The entire application was built using Jdeveloper 11.1.1.5 using a pre-constructed WSDL. The SOA suite is 11.1.1.5
Any pointers will be really appreciated.
Thanks
The composite is this:
<?xml version="1.0" encoding="UTF-8" ?>

<composite name="SOA2" revision="1.0" label="2013-02-28_14-25-14_553"
mode="active" state="on" xmlns="http://xmlns.oracle.com/sca/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:ui="http://xmlns.oracle.com/soa/designer/">
<import namespace="http://soa/sf/login" location="loginToSFDC.wsdl"
importType="wsdl"/>
<service name="bpelprocess1_client_ep" ui:wsdlLocation="loginToSFDC.wsdl">
<interface.wsdl interface="http://soa/sf/login#wsdl.interface(loginPort)"/>
<binding.ws port="http://soa/sf/login#wsdl.endpoint(bpelprocess1_client_ep/loginPort_pt)"/>
</service>
<component name="BPELProcess1" version="2.0">
<implementation.bpel src="BPELProcess1.bpel"/>
<property name="bpel.config.transaction" type="xs:string" many="false">required</property>
</component>
<wire>
<source.uri>bpelprocess1_client_ep</source.uri>
<target.uri>BPELProcess1/bpelprocess1_client</target.uri>
</wire>
</composite>
The WSDL used to generate the BPEL is:
<?xml version= '1.0' encoding= 'UTF-8' ?>
<definitions
targetNamespace="http://soa/sf/login"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns1="http://soa/sf/login"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:flt="urn:fault.partner.soap.sforce.com"
xmlns:obj="urn:sobject.partner.soap.sforce.com"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:typ="urn:partner.soap.sforce.com"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
>
<types>
<xsd:schema targetNamespace="http://uk.gov.fca.sf/login" elementFormDefault="qualified" xmlns:tns1="http://uk.gov.fca.sf/login"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:flt="urn:fault.partner.soap.sforce.com"
xmlns:obj="urn:sobject.partner.soap.sforce.com" xmlns:typ="urn:partner.soap.sforce.com"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/">
<xsd:import namespace="urn:partner.soap.sforce.com" schemaLocation="xsd/partner_types.xsd"/>
<xsd:import namespace="urn:fault.partner.soap.sforce.com" schemaLocation="xsd/partner_faults.xsd"/>
<xsd:import namespace="urn:sobject.partner.soap.sforce.com" schemaLocation="xsd/partner_objects.xsd"/>
</xsd:schema>
</types>
<message name="loginInMessage">
<part name="loginIn" element="typ:login"/>
<part name="LoginScopeHeaderIn" element="typ:LoginScopeHeader"/>
<part name="CallOptionsIn" element="typ:CallOptions"/>
</message>
<message name="loginOutMessage">
<part name="return" element="typ:loginResponse"/>
</message>
<portType name="loginPort">
<operation name="loginOp">
<input message="tns1:loginInMessage"/>
<output message="tns1:loginOutMessage"/>
</operation>
</portType>
<binding name="loginPortSOAP11Binding" type="tns1:loginPort">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="loginOp">
<soap:operation style="document" soapAction="http://soa:8101/login/loginOp"/>
<input>
<soap:body use="literal" parts="in"/>
</input>
<output>
<soap:body use="literal" parts="return"/>
</output>
</operation>
</binding>
<binding name="loginPortSOAP12Binding" type="tns1:loginPort">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="loginOp">
<soap12:operation style="document" soapAction="http://uk.gov.fca.sf:7101/login/loginOp" soapActionRequired="false"/>
<input>
<soap12:body use="literal" parts="in"/>
</input>
<output>
<soap12:body use="literal" parts="return"/>
</output>
</operation>
</binding>
<service name="loginSrvc">
<port name="login_port_11" binding="tns1:loginPortSOAP11Binding">
</port>
<port name="login_port_12" binding="tns1:loginPortSOAP12Binding">
</port>
</service>
<partnerLinkType name="ProviderRole"
xmlns="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<role name="Role1">
<portType name="tns1:loginPort"/>
</role>
</partnerLinkType>
</definitions>

Hi,
I don't see a loginPort_pt port in the wsdl, but it is referenced by the composite...
There's only ports login_port_11 and login_port_12 defined...
Cheers,
Vlad

Error Generating WebService for SOAP over JMS

Hi,
I've been tring to create an addition web service thta takes two input and returns the sum. I was able to generate the WSDL using JDevelopers GUI tool for generating WSDL, but I notices that there was no transport layer, in thebinding that suppoerted SOAP, and the "create web service from WSDL" wizard also gave and error message:
oracle.jdeveloper.webservices.model.WebServiceException: The chosen WSDL contains no SOAP 1.1 bindings and is therefore unsuitable for generation of a JAX-RPC web service for WLS. Only SOAP 1.1 bindings are supported for generation of JAX-RPC web services for deployment to WLS.
This is the WSDL I created:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="http://www.example.org/addition"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.example.org/addition"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:jms="http://schemas.xmlsoap.org/wsdl/jms/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/">
<types>
<xsd:schema targetNamespace="http://www.example.org/addition/types"
elementFormDefault="qualified"/>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:add="http://www.example.org/addition"
targetNamespace="http://www.example.org/addition"
elementFormDefault="qualified">
<xsd:element name="additionInput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="a" type="xsd:int"/>
<xsd:element name="b" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="additionOutput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sum" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
<message name="AdditionInputMessage">
<part name="payload" element="tns:additionInput"/>
</message>
<message name="AdditionOutputMessage">
<part name="payload" element="tns:additionOutput"/>
</message>
<portType name="AdditionPortType">
<operation name="addition">
<input message="tns:AdditionInputMessage"/>
<output message="tns:AdditionOutputMessage"/>
</operation>
</portType>
<binding name="AdditionPortTypeJMSBinding" type="tns:AdditionPortType">
<jms:binding type="ObjectMessage"/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap typeName="tns:additionInput" formatType=""/>
<format:typeMap typeName="tns:additionOutput" formatType=""/>
</format:typeMapping>
<operation name="addition">
<input>
<jms:input parts="payload"/>
<jms:property name="payloadProperty" part="payload"/>
</input>
<output>
<jms:output parts="payload"/>
<jms:property name="payloadProperty" part="payload"/>
</output>
</operation>
</binding>
<service name="AdditionPortType">
<port name="AdditionPortTypePort" binding="tns:AdditionPortTypeJMSBinding"/>
</service>
</definitions>
Could someone please help me out? I've been struggling with this problem for two weeks and can't make any headway. It's really driving me nuts. I've looked all over the web, and while everyone agrees that SOAP over JMS is possible, no one sems to have a working solution. One example I was able to get hold of used ant for deployment, but the deploy task failed when I ran it. Please, please help me.

Hi,
I've been tring to create an addition web service thta takes two input and returns the sum. I was able to generate the WSDL using JDevelopers GUI tool for generating WSDL, but I notices that there was no transport layer, in thebinding that suppoerted SOAP, and the "create web service from WSDL" wizard also gave and error message:
oracle.jdeveloper.webservices.model.WebServiceException: The chosen WSDL contains no SOAP 1.1 bindings and is therefore unsuitable for generation of a JAX-RPC web service for WLS. Only SOAP 1.1 bindings are supported for generation of JAX-RPC web services for deployment to WLS.
This is the WSDL I created:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="http://www.example.org/addition"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.example.org/addition"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:jms="http://schemas.xmlsoap.org/wsdl/jms/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/">
<types>
<xsd:schema targetNamespace="http://www.example.org/addition/types"
elementFormDefault="qualified"/>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:add="http://www.example.org/addition"
targetNamespace="http://www.example.org/addition"
elementFormDefault="qualified">
<xsd:element name="additionInput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="a" type="xsd:int"/>
<xsd:element name="b" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="additionOutput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sum" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
<message name="AdditionInputMessage">
<part name="payload" element="tns:additionInput"/>
</message>
<message name="AdditionOutputMessage">
<part name="payload" element="tns:additionOutput"/>
</message>
<portType name="AdditionPortType">
<operation name="addition">
<input message="tns:AdditionInputMessage"/>
<output message="tns:AdditionOutputMessage"/>
</operation>
</portType>
<binding name="AdditionPortTypeJMSBinding" type="tns:AdditionPortType">
<jms:binding type="ObjectMessage"/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap typeName="tns:additionInput" formatType=""/>
<format:typeMap typeName="tns:additionOutput" formatType=""/>
</format:typeMapping>
<operation name="addition">
<input>
<jms:input parts="payload"/>
<jms:property name="payloadProperty" part="payload"/>
</input>
<output>
<jms:output parts="payload"/>
<jms:property name="payloadProperty" part="payload"/>
</output>
</operation>
</binding>
<service name="AdditionPortType">
<port name="AdditionPortTypePort" binding="tns:AdditionPortTypeJMSBinding"/>
</service>
</definitions>
Could someone please help me out? I've been struggling with this problem for two weeks and can't make any headway. It's really driving me nuts. I've looked all over the web, and while everyone agrees that SOAP over JMS is possible, no one sems to have a working solution. One example I was able to get hold of used ant for deployment, but the deploy task failed when I ran it. Please, please help me.

"Channel started but inactive" in RWB Monitor for SOAP sender channel

Dear XI specialists,
I have configured a communication scenario involving SOAP Adapter (sender) usage, but I'm facing the issue when testing the scenario. The problem is that none of messages are coming into the SOAP Adapter (checked via TCode SXI_MONITOR in XI) when using 3rd party SOAP-clients (XML Spy, soapUI) based on WSDL-file generated and exported from XI.
I checked the sender communication channel for SOAP Adapter - it is activated in Integration Builder's Directory. SOAP Adapter itself is also started.
I checked Runtime Workbench monitors and in the Communication Channels Monitor of the Components Monitor received the warning saying "Channel started but inactive" for my configured channel as well as for other channels working on SOAP Adapter.
Activities which were performed (in the order in which they were performed and results tested):
1. the configuration channel restart;
2. the communication channel re-activation and further re-start;
3. SOAP Adapter restart;
4. XI system's Java instance restart.
All mentioned activities didn't give any positive effect in part of this issue resolution.
On the other hand, if I use test message functionality of the Runtime Workbench (Component Monitor), then messages are seen in SXI_MONITOR and expected response messages are also returned to XI from integrated business system.
Would you please advise what can be checked else here and where the root of the problem may be detected?
All your answers and feedback will be greatly appreciated and awarded accordingly.
Many thanks in advance and my regards,
Vadim

Dear all,
Thank you for your input! Unfortunately, the problem still exists after testings and checkings which you suggested.
TO Seshagiri:
I checked message monitor and found only several messages for the required sender/receiver services pair in the used namespace - all of them were successfully processed (these are messages which I sent by means of RWB Component Monitor's test message functionality).
TO Sarvesh:
Yes, sender agreement is configured properly. I configured it when configuring communication scenario in the Configuration Wizard and then manually re-checked its definition. Moreover, when performing Test Configuration in ID, I received positive results.
TO Nallam Guna:
I cleared Data Cache in Integration Builder, but this didn't help.
TO Gujjeti:
I'm on SAP NetWeaver 2004s PI 7.0. Service Pack level for PI is 13.
TO Durga:
Thank you for provided links! I have already had a look at them - but proposed solutions doesn't seem to be working in my situation.
Thank you all once again for your prompt answers! I really appreciate your attempts in helping me!
I would appreciate if you could share any further ideas on this issue.
My best regards,
Vadim

Synchronous scenario for SOAP to PROXY

Dear Experts,
    I will be working on the following scenarios.
XI will expose the Outbound Interfaces as a Web Service Interface. Web Service Description (WSDL File) will be generated for the Interfaces in Integration directory. DSS (decision support system) will use this WSDL file to define the data types and develop the Web Application. The Web Application sender sends the request message (Start Date, End Date and Table name) synchronously to XI using SOAP Adapter as communication channel. XI sends the message to SAP R/3 via ABAP Proxy. The ABAP Proxy extracts the data from SAP R/3 and sends the data back to XI . XI further passes on the data to DSS.
Request
Sender Application:     DSS
Target Application:     SAP R/3
Sender XI Adapter:     SOAP
Receiver XI Adapter:     XI
Response
Sender Application:     SAP R/3
Target Application:     DSS
Sender XI Adapter:     XI
Receiver XI Adapter:     SOAP
It's a synchronous interface. Please help me out right from the SLD design. I just want an idea how to proceed with this.
How many mapping will have to do? also very important point , can any one help me out, how to write an ABAP proxy for the same. I will have rewards for every answer as time is very very less and work is more.
Thanks
Veeru

Viru ,
So the Business systems will Web as ABAP for ECC and other will be third party. I am right.
Yes
Can u suggest me how to proceed with the mapping. Any snap shots for this scenario?
Mapping will be simple using Mapping editor in IR .
If u have please provide me.
for your refernce :
Few proxy based scenarios :
http://help.sap.com/saphelp_nw04/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
/people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7d4db211-0d01-0010-1e8e-9b07fc2113ab
http://help.sap.com/saphelp_bw30b/helpdata/en/64/30063c66171b3de10000000a11402f/content.htm
I am working on XI 3.0 for this scenario. how to handle the webservices here.
for Web service based scenarios :
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
Regards ,

Invalid content type for SOAP: TEXT/HTML

Hi guys,
Im trying to sending a message via sender soap adapter and Im receiving this error:
Exception caught by adapter framework: invalid content type for SOAP: TEXT/HTML
I already have read most off all posts about this error in this forum. So, if I understand, this error means that my receiver soap adapter cant reach the web service provider and an HTTP error notification is sent to calling application. Although, the SOAP adapter doesnt understand this kind of errors (ex. 404 not found -> SOAP call has no error codes and use the HTTP codes for effect) and this happening because the error is in text/html format and SOAP adapter is waiting a response in text/xml.
This is a simple calculator web service that receives two arguments and returns the sum as a result. (Like Siva Maranani weblog /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi )
The web service is published on SAP Enterprise Portal and it works fine.
- The login works fine
    User: ex30268
    Pwd: 12345678
- We dont have certificates and proxy server.
This is the address in my receiver soap adapter: http://intranetcorpdev.edp.pt:54700/CalculatorWebService/Config1?style=document
I already checked the settings of my receiver soap adapter and did a little test, enabling the parameter Do Not Use SOAP Envelop only in receiver adapter. And the result is an exception during mapping!!! What is means this error?
Does anybody know how to solve this issue?
Thanks in advance.
Cheers,
Ricardo.

Hi all,
Please forgive me for boring you again with this subject, but I havent yet solved this issue, I still receive the following message and Im getting quite worried
>>> Invalid content type for SOAP: TEXT/HTML
Im following Siva Maranani web log (Invoke Webservices using SAPXI) and I will describe the steps that I did:
<b>Integration Repository:</b>
     An Inbound synchronous Message Interface (CalculatorWS_IN_MI) using the message types in external definition (WSDL from web service hat I want to invoke).
     The other necessary data types (Calc_input_DT has 2 parameters>arg1 and arg2. and Calc_out_DT has 1 param> result) and corresponding Message types.
     An Outbound synchronous Message Interface (Calc_OUT_MI) using the message types defined in Integration Directory.
     2 Message mappings (request and response) and 1 Interface mapping.
<b>Integration Directory:</b>
     A scenario calls WebServices.
     2 business services (webservice and webservice_calc).
     A Receiver determination with webservice as a sender service (note: this sender is simulated from the WSNavigator from an Enterprise Portal that I have installed locally in my laptop) the interface is (Calc_OUT_MI).
     An Interface determination with webservice_calc as a receiver service and the corresponding mapping interface and SOAP receiver channel.
Configurations of SOAP receiver channel:
Target URL: http://intranetcorpdev.edp.pt:54700/CalculatorWebService/Config1?style=document
User: ex30268
Pwd: 12345678
I have picked only the parameters Use Encoded Headers and Use Query String activated. Im not using any kind of certificates or proxy servers.
A call tentative:
Request
POST /XISOAPAdapter/MessageServlet?channel=:WebService:SOAPSenderChannel&version=3.0&Sender.Service=WebService&Interface=http%3A%2F%2Fswitching%2Fxi%5ECalc_OUT_MI HTTP/1.1
Host: ed19dci1f.appl.edinfor.pt:54900
Content-Type: text/xml; charset="UTF-8"
Connection: close
Cookie: <value is hidden>
Cookie: <value is hidden>
Authorization: <value is hidden>
SOAPAction: "http://sap.com/xi/WebService/soap1.1"
Content-Length: 407
Response
HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Fri, 12 May 2006 08:24:18 GMT
<?xml version='1.0'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
    <SOAP:Fault>
      <faultcode>SOAP:Server</faultcode>
      <faultstring>Server Error</faultstring>
      <detail>
        <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
          <context>XIAdapter</context>
          <code>DeliveryException</code>
          <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:451)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:125)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:831)
     at com.sap.engine.frame.core.thread.Task.run(Task.java(Compiled Code))
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java(Compiled Code))
          ]]></text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I think that I have tried everything and read almost of posts, web logs, SDN community contribution and the info in help.sap.com, but Im feeling unable to solve this kind of issue. Im afraid that I was missed something. So thats the reason to describe here all the steps that I have done.
I hope somebody knows how to solve this issue or give me something that can help me find the end of this road
Thanks for all.
Cheers,
Ricardo.

DeliveryException: invalid content type for SOAP: TEXT/PLAIN; HTTP 302 Move

Hi everyone,
Hello all,
I have an RFC->XI->Web Service (SOAP) synchronous scenario.
I'm trying to send a message from the the RFC, and in the message monitoring (SXMB_MONI) I'm getting this error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/PLAIN; HTTP 302 Moved Temporarily</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have as the TARGET URL: http://webservices.iter.dk/calculator.asmx?WSDL
SOAP ACTION: http://www.iter.dk/webservices/calculator.asmx/Add
As the content type in the WSDL file: application/text
What could be wrong? thanks...
Felipe

Hi Felipe
This i think is due to incorrect address or redirection failure which is one of the major reason for 302 as per my knowledge.
You try to post the content and test it without using XI. Download SOAP UI and test it once and let me know
http://www.soapui.org/
helpful blog
Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 ***
Thanks
Gaurav

: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect

Hi Experts,
I am facing with the flowing error when we are receiving for the soap receiver chanel.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect
is their any content type to give in soap receiver channel.
please let me know.
Regards
Raju

I think the message is misleading. HTTP 302 meaning is that the url specified in not found or invalid for that service. You might want to check with external system that the specified URL in the SOAP receiver communication channel is right? Also you can find the URL from the WSDL itself. Similar test do it outside PI using the SOAPUI or XMLSPY and see the response error.

Invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

Hi,
I have mentioned some issues that I am facing in SOAP receiver adapter:
[XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 404 Not Found;
Apart from that I am trying with unchecking 'Do Not Use SOAP envelope' and by using MessageTransformBean, for which I am getting the following error:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
Need your help in resolving this.
Regards,
Vishal

I have some ideas which will help you out. Check the below option one by one:
1. Check receiver server is accessable from XI/PI system through IP address in command prompt.
2. Check whether any PORT is enabled for this server. ex: http://ipaddress:portno/XXX/XXX.asmx
3. You can download webservice tool(SOAP UI and etc..)to check your webservice(WSDL) file able to connect the server by importing webservice file in this tool.
4. Sometime customer may updated in their application(coding and etc) and not given the updated webservice file to us. so make sure you got updated one.
Regards,
Senthil

Invalid content type for SOAP: TEXT/HTML on Reciever SOAP

HI All,
I have a reciever SOAP channel setup to send a message and its attachments to a supplier. The recieving application is as follows:
"It just receives the stream or contentStream and print out the content. It's just a test to see what you sent to us. It processes all http/https messages."
If I leave the SOAP Envelope on I get the content type error in the header. If I turn the Enveloper off, I get a successful post. They are try to trap what I send to build a SOAP processor, so they want the SOAP envelope. What could be causing this?
Kind Regards,
Chris

Hi Richard,
The web service address that we must type in target URL of receiver soap adapter is the address to the WSDL. To be sure types this address in your browser and you must see a WSDL code of the webservice that you want invoke.
The reason that you are getting Delivery Exception: invalid content type for SOAP:TEXT/HTML. is because you are trying to invoke a web service with wrong address.
So, when SOAP receiver adapter try to put the message on the target side, it cant and automatically receives an HTTP acknowledge in HTML format. As SOAP adapter doesnt understand HTML code only XML code, it cant recognize what kind of error is and generates an exception indicating that the content type is invalid.
Delivery Exception: invalid content type for SOAP:TEXT/HTML is equal to any HTTP code, I have almost sure that HTTP code is a 404 Not Found, but you cant see it...
Post the URL here for I can check
Cheers,
Ricardo.

Invalid content type for SOAP

Hi all,
We have configured a proxy to soap scenario, where the sender is SAP system and our receiver system is a third party tool.
We are testet the webservice and getting success response from SOAP UI. Also the mapping seems to be ok.
But if we test the scenario, we are getting following error;
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Found
Please, can anyone assist me in this matter?
Kind Regards,
PM

Hi Gurus,
we are getting also with opensource web service same error.
h2.
Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Found
Here is detailled described.
SENDER XML
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Add xmlns:ns0="http://www.deeptraining.com">
   <ns0:dbl1>23</ns0:dbl1>
   <ns0:dbl2>21</ns0:dbl2>
</ns0:Add>
XSLT CODE
<?xml version='1.0'?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://www.deeptraining.com">
<xsl:template match="/">
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:deep="http://www.deeptraining.com">
   <soapenv:Header/>
   <soapenv:Body>
      <deep:Add>
         <deep:dbl1><xsl:value-of select="ns0:Add/ns0:dbl1"/></deep:dbl1>
         <deep:dbl2><xsl:value-of select="ns0:Add/ns0:dbl2"/></deep:dbl2>
      </deep:Add>
   </soapenv:Body>
</soapenv:Envelope>
</xsl:template>
</xsl:stylesheet>
OUTPUT XML
<?xml version="1.0"?>
<soapenv:Envelope xmlns:deep="http://www.deeptraining.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://www.deeptraining.com">
     <soapenv:Header/>
     <soapenv:Body>
          <deep:Add>
               <deep:dbl1>23</deep:dbl1>
               <deep:dbl2>21</deep:dbl2>
          </deep:Add>
     </soapenv:Body>
</soapenv:Envelope>
TARGET URL : http://www.deeptraining.com/webservices/mathservice.asmx?WSDL
SOAP ACTION CODE: http://www.deeptraining.com/Add
Maybe Firewall issue?
Warm Regards,
PM

EROR: java.io.IOException: invalid content type for SOAP: TEXT/HTML

hi group,
my problem is related to scenario HTML to WebService in which im trying to send a request to a free webservice on internet and retrieving the response back and showing it in my html page.
scenario in detail:
i have a html page deployed on my tomcat server at my local m/c. in which im taking a email string and sending it to webservice which checks whether the email string has a valid email format or not and in response, webservice returns a boolean true/false depending on the email string. i want to show this boolean result n my html page.i have configured HTTP adaptor and SOAP adaptor for this and interfaces are scynchronus.
im able to send my request to webservice and getting the response also...i checked in trace..it shows message request sent and response recieved...here is the trace..
http://hcl3sap:50000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = PIISUSER</Trace>
<Trace level="3" type="T">Cached =</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
but i get an error java.io.IOException: invalid content type for SOAP: TEXT/HTML after that,
Does anyone know where im going wrong....
regrds

you are very correct..i used SOAP reciever as http://www.webservicex.net/ValidateEmail.asmx?wsdl and SOAP Action as http://www.webservicex.net/IsValidEmail but getting the same error.
and if you look in the trace above it says that my request actually went to webservice and got a response also (response code 200) but i think after recieving the message from webservice something is wrong. either mapping is not correct...(but i tested that ..it works fine) or could be my company firewall is prohibiting the message sent by webservice to XI server (i have given proxy settings with password also)...im NOT sure on this ....
second thing i noticed in moni while examining the trace was....message payload under "Message Branch According to Receiver List " shows this value
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:IsValidEmail xmlns:ns1="http://www.webservicex.net">
<ns1:Email>samWhgf.com</ns1:Email>
</ns1:IsValidEmail>
and then in just next step "Request Message Mapping" payload is
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:IsValidEmail xmlns:ns1="http://www.webservicex.net" />
i dont know really why payload is getting appended and if it is correct or not? but after this step further payload goes in this appended format only till call adaptor...if this is so i assume my message is going to webservice as
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:IsValidEmail xmlns:ns1="http://www.webservicex.net" />
which is not the proper format to be recieved by the webservice without any input value i.e "samWhgf.com"
im confused on this ..whether this is the route cause or any other...i have been trying to figure out the root cause from some days but still unsuccessful.
please provide ur valuable inputs.
regrds
Sameer

WSDL 1.1 Binding Extension for SOAP 1.2

Similar Messages

Maybe you are looking for