WSDL SOAP Test With soapui

Question

I have tested my web services  wsdl soap  with soapui  and i have the errors   http log   error 400 BAD REQUEST   What can be the error please with my wsdl    error log    un Jun 05 14 10 37 CEST 2011 ERROR javax wsdl WSDLException  WSDLException  at  html   faultCode INVALID WSDL  Expected element   http   schemas xmlsoap org wsdl  definitions      javax wsdl WSDLException  WSDLException  at  html   faultCode INVALID WSDL  Expected element   http   schemas xmlsoap org wsdl  definitions       at com ibm wsdl xml WSDLReaderImpl checkElementName Unknown Source      at com ibm wsdl xml WSDLReaderImpl parseDefinitions Unknown Source      at com ibm wsdl xml WSDLReaderImpl readWSDL Unknown Source      at com ibm wsdl xml WSDLReaderImpl readWSDL Unknown Source      at com ibm wsdl xml WSDLReaderImpl readWSDL Unknown Source      at com ibm wsdl xml WSDLReaderImpl readWSDL Unknown Source      at com ibm wsdl xml WSDLReaderImpl readWSDL Unknown Source      at com eviware soapui impl wsdl support wsdl WsdlInterfaceDefinition load WsdlInterfaceDefinition java 48      at com eviware soapui impl wsdl support wsdl WsdlContext loadDefinition WsdlContext java 66      at com eviware soapui impl wsdl support wsdl WsdlContext loadDefinition WsdlContext java 30      at com eviware soapui impl support definition support AbstractDefinitionContext cacheDefinition AbstractDefinitionContext java 264      at com eviware soapui impl support definition support AbstractDefinitionContext access 400 AbstractDefinitionContext java 44      at com eviware soapui impl support definition support AbstractDefinitionContext Loader construct AbstractDefinitionContext java 230      at com eviware soapui support swing SwingWorkerDelegator construct SwingWorkerDelegator java 46      at com eviware soapui support swing SwingWorker 2 run SwingWorker java 140      at java lang Thread run Thread java 637

User · Accepted Answer

definitions is a root element of WSDL so it looks like you are not loading WSDL   Edit   I tested it and it looks like the whole problem is with your web server  Your web server returns WSDL to browser but it doesn t return it to any tool because these tools are using very minimalistic HTTP requests without many HTTP headers  One of missing headers is Accept  Once this header is not included in the request your server throws HTTP 400 Bad request   The easy approach to continue is opening WSDL in the browser  save the wsdl to a file and import that file to soapUI instead of the WSDL from URL

User · Answer

A likely possibility is that your browser reaches your web service through a proxy  and SoapUI is not configured to use that proxy   For example  I work in a corporate environment and while my IE and FireFox can access external websites  my SoapUI can only access internal web services    The easy solution is to just open the WSDL in a browser  save it to a  xml file  and base your SoapUI project on that  This won t work if your WSDL relies on external XSDs that it can t get to  however

User · Answer

You can try opening the wsdl in web browser and saving with  wsdl extension  And set the WSDL in SOAP UI project to this  wsdl file  This really works

User · Answer

Another possibility is that you need to add  wsdl at the end of your service url for SoapUI  That one got me as I m used to WCFClient which didn t need it

User · Answer

I faced the same exception while trying to test my web-services deployed to WSO2 ESB    WSO2 generated both wsdl and wsdl2  I tried to pass a wsdl2 URL and got the above exception  Quick googling showed me  that one of differences between wsdl1 1 and wsdl2 0 is replacing  definitions  element with  description   Also  I found out  that SoapUI does not support wsdl2   Therefore  for me the solution was to use wsdl1 url instead of wsdl2

User · Answer

yes  first ensure you added   wsdl  to your  http      whatever svc  link   That didn t fix my problem  though  I had to create a new WCF project from the beginning and manually copy the code  That fixed it  Good luck     And most important     When you change a namespace in your code  also make sure you change it in web config

User · Answer

For anyone hitting this issue in the future  the specific situation here   the server isn t sending back the WSDL properly   may or may not always be relevant  but two key aspects should always be    The message faultCode INVALID WSDL  Expected element   http   schemas xmlsoap org wsdl  definitions  means that the actual content returned is not XML with a base element of  definitions  in the WSDL namespace  The message WSDLException  at  html  tells you an important clue about what it did find     for this example   html strongly implies that a normal webpage was returned  rather than a WSDL  Another common situation is seeing something like  soapenv Reason  which would indicate that the server was trying to treat it as a SOAP call     for example  this can happen if your URL is for the  base  service URL rather than the WSDL

[web-services] WSDL/SOAP Test With soapui

Examples related to web-services

Examples related to wsdl

Examples related to soapui