Search code examples
web-servicessoapwsdljax-wsglassfish-4.1

What difference step is happening while importing WSDL via browser Vs SOAPUI


I have a well reported problem with a simple WS deployed in Glassfish 4.1 , where I get the WSDL in browser but cant import it in SOAP UI or Eclipse(Kepler) .

IWAB0135E An unexpected error has occurred. WSDLException WSDLException: faultCode=OTHER_ERROR: this

My question is : What extra thing is happening while trying to access this location from SOAP UI / Eclipse WebService explorer Vs via browser ? I would like to know what other areas I need to look at to trouble shoot this issue .


Solution

  • When loading a WSDL trough SOAP UI, it tries to parse it and does some validations of the WSDL in order to create a SOAP UI project and generate the empty requests for you. Eclipse also does these validations (On validate in the context menu, when a .WSDL is opened or when saving a .WSDL) - I've found them even more strict than the SOAP UI ones.

    On the other hand, the browser doesn't do validation of the wsdl content, it just displays it as it is, and applies some default colours for rendering xml in order to make it more readable. But it would not complain if the wsdl is not formed correctly.