Geek Answers Handbook

Soap parsing wsdl error: Unexpected element: TAG_END

I have an error importing a WSDL definition from an ASP.NET version 4 Visual Studio 2010 Express project in SOAPUI 4.5.1

URL will look like

http://localhost:7929/ws/AX.asmx?WSDL

Error generated

 Error loading [http://localhost:7929/ws/AX.asmx?WSDL]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected element: TAG_END

Error tracing:

 com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:138) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:535) ...

Any suggestions are welcome!

+7
source share
3 answers

I had the same problem with Soap UI 5.2.0

The solution for me was to disable the proxy (as suggested by @ user518066)

enter image description here

+10
source

The problem is that soapui does not know where to find the schema file. If your wsdl is deployed to the server, it will return the URL of the xsd file for inclusion, and soapui can find it ....

+5
source

I had the same problem, after a few hours I found that the problem was related to IPv6.

When I go to the service url, I can see and check the wsdl file. There were no problems.

 http://localhost/SoapServer.php?wsdl

But when I add this URL to SoapUI, it gives an Unexpected element: TAG_END . I found the reason using cURL, curl http://localhost/SoapServer.php?wsdl returns 404 !!

So I realized that my Apache listens for both IPv4 and IPv6, the browser goes to IPv6 and gets wsdl, but cURL and SoapUI go to IPv4 and get a 404 error.

I disabled IPv6 on my Apache by deleting the line Listen [::0]:80 in the httpd.conf file, this solved the problem.

+2
source

More articles:


All Articles