cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP:14 - Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/

Former Member
0 Kudos

Hello Experts,

I created proxy from local WSDL. Than I assigned local port into proxy class.

When I tried call method i got following error message:

SOAP:14 - Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/

Below you can find definition from wsdl:

<definitions

xmlns="http://schemas.xmlsoap.org/wsdl/"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

name="IWebXServiceservice"

targetNamespace="http://localhost/"

xmlns:tns="http://localhost/"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

(...)

Could you help?

Thanks in advance,

Ed

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

hi,

I've created a full how-to in the wiki:

http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=250513414

Roland

Former Member
0 Kudos

No this is not part of the WSDL but the SOAP Message is created during runtime and it should have a root tag <env:Envelope>.

Your wsdl is a service type , correct? How did you start the WS call, via SPROXY or an application report?

Former Member
0 Kudos

I created proxy from local file (wsdl).

Than I created logical port (I didn't put 'SOAP Action' ur for methods because I couldn't find it in wsdl file).

And than i created test report and run it from se38.

Former Member
0 Kudos

Hello edward,

I got similar issues like you, especially the one you mentioned in your first post back in April:

This one is closed, but how could you go further? Looks like you did as you got the next challenging errors

Former Member
0 Kudos

Re,

as I followed this how-to:

http://www.sapdev.co.uk/sap-webapps/sap-webservices/ws_abapproxy.htm

In step 4, the URL to enter into the "Call Parameters" of LPCONFIG was equal to the WSDL location.

But the URL should NOT end with "?WSDL". Otherwise you might get the error "Unexpected element -el=definitions ns =http://schemas.xmlsoap.org/" (or similar, as this does not run the webservice, furthermore it returns the WSDL which starts with definitions...)

Former Member
0 Kudos

Hi, the error means that it is not sent a SOAP Envelope or SOAP message which starts with <env:Envelope> element , some header and body SOAP elements.

How did you configure the Logical Port for your Web Service consumer. Please use SOAMANAGER transaction to configura a LP from a WSDL file and use this LP when you execute the call. If you set LP = default this LP will be automatically used when you execute the WS

Former Member
0 Kudos

Hi,

I don't have in wsdl file part for 'SOAP Envelope or SOAP message which starts with <env:Envelope>'. Should I add that part?

LP works correct. It was created using LPCONFIG.