cancel
Showing results for 
Search instead for 
Did you mean: 

No SOAP Envelope but 1 {http://schemas.xmlsoap.org/wsdl/}definitions; HTTP

former_member474221
Participant
0 Kudos

Hi

I created a webservice from a inbound proxy in soamanager....

also i specified the user id and pwd in receiver soap channel ....

but i am getting the following error in the response message

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK</SAP:AdditionalText>

What could be the reason.....if i do not call the webservice and directly call the proxy it works..

Accepted Solutions (0)

Answers (1)

Answers (1)

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

have you specified "no soap" checkbox in the communication channel ?

Regards,

Michal Krawczyk

former_member474221
Participant
0 Kudos

i tried the "no soap" check box ans now i am not getting any error...

however the response message does not contain the response.....it only contains the service definition...

why am i not getting the actual response that should be there in the OUTPUT node

The reponse message is having following in the payload

<?xml version="1.0" encoding="utf-8" ?>

- <wsdl:definitions targetNamespace="http://test.com/ws/abap" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://test.com/ws/abap" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

- <wsdl:documentation>

<sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />

</wsdl:documentation>

<wsp:UsingPolicy wsdl:required="true" />

- <wsp:Policy wsu:Id="BN_BN_zasd">

<saptrnbnd:OptimizedXMLTransfer uri="http://xml.sap.com/2006/11/esi/esp/binxml" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" />

<saptrnbnd:OptimizedXMLTransfer uri="http://www.w3.org/2004/08/soap/features/http-optimization" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" />

<sapattahnd:Enabled xmlns:sapattahnd="http://www.sap.com/710/features/attachment/">false</sapattahnd:Enabled>

- <wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">

- <wsp:All>

- <sp:TransportBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wst="http://docs.oasis-open.org/ws-sx/ws-trust/200512" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex">

- <wsp:Policy>

- <sp:TransportToken>

- <wsp:Policy>

- <sp:HttpsToken>

- <wsp:Policy>

<sp:HttpBasicAuthentication />

</wsp:Policy>

</sp:HttpsToken>

</wsp:Policy>

</sp:TransportToken>

- <sp:AlgorithmSuite>

- <wsp:Policy>

<sp:TripleDesRsa15 />

</wsp:Policy>

</sp:AlgorithmSuite>

- <sp:Layout>

- <wsp:Policy>

<sp:Strict />

</wsp:Policy>

</sp:Layout>

</wsp:Policy>

</sp:TransportBinding>

</wsp:All>

</wsp:ExactlyOne>

</wsp:Policy>

- <wsp:Policy wsu:Id="IF_IF_si_in_syn">

- <sapsession:Session xmlns:sapsession="http://www.sap.com/webas/630/soap/features/session/">

<sapsession:enableSession>false</sapsession:enableSession>

</sapsession:Session>

<sapcentraladmin:CentralAdministration xmlns:sapcentraladmin="http://www.sap.com/webas/700/soap/features/CentralAdministration/" wsp:Optional="true" />

</wsp:Policy>

- <wsp:Policy wsu:Id="OP_IF_OP_si_in_syn">

<sapcomhnd:enableCommit xmlns:sapcomhnd="http://www.sap.com/NW05/soap/features/commit/">false</sapcomhnd:enableCommit>

<sapblock:enableBlocking xmlns:sapblock="http://www.sap.com/NW05/soap/features/blocking/">true</sapblock:enableBlocking>

<saptrhnw05:required xmlns:saptrhnw05="http://www.sap.com/NW05/soap/features/transaction/">no</saptrhnw05:required>

<saprmnw05:enableWSRM xmlns:saprmnw05="http://www.sap.com/NW05/soap/features/wsrm/">false</saprmnw05:enableWSRM>

</wsp:Policy>

- <wsdl:types>

- <xsd:schema targetNamespace="http://test.com/ws/abap" xmlns:xi0="http://test.com/ws/abap" xmlns="http://test.com/ws/abap">

- <xsd:complexType name="dt_mat">

- <xsd:sequence>

- <xsd:element name="rows" maxOccurs="unbounded">

- <xsd:complexType>

- <xsd:sequence>

<xsd:element name="matno" type="xsd:string" />

<xsd:element name="mattext" type="xsd:string" />

........

.....

MichalKrawczyk
Active Contributor
0 Kudos

hi,

1. you are supposed not to use "no soap" for a standard SOAP call

2. can you test your WSDL in SOAPUI (free tool) to check it the WS is working ?

Thank you,

Regards,

Michal Krawczyk