Forum Discussion

atlsgnz's avatar
atlsgnz
Occasional Contributor
13 years ago

No context found for request error on localhost

I have a web service deployed on Tomcat that I imported into soapUI using the wsdl on our development server. I then added two more endpoints for that project, one on our test server and one on my loc...
atlsgnz's avatar
atlsgnz
Occasional Contributor
13 years ago
I'm not seeing one. This is the log from a working message:


DEBUG:>> "POST /services/MyService/webservices/myendpoint HTTP/1.1[\r][\n]"
DEBUG:>> "Accept-Encoding: gzip,deflate[\r][\n]"
DEBUG:>> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
DEBUG:>> "SOAPAction: "http://mycompany.com/getXML"[\r][\n]"
DEBUG:>> "Content-Length: 322[\r][\n]"
DEBUG:>> "Host: dev-server.mycompany.com[\r][\n]"
DEBUG:>> "Connection: Keep-Alive[\r][\n]"
DEBUG:>> "User-Agent: Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]"
DEBUG:>> "[\r][\n]"
DEBUG:>> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://mycompany.com/types/">[\n]"
DEBUG:>> "   <soapenv:Header/>[\n]"
DEBUG:>> "   <soapenv:Body>[\n]"
DEBUG:>> "      <typ:getXMLElement>[\n]"
DEBUG:>> "         <typ:pNumDays>40</typ:pNumDays>[\n]"
DEBUG:>> "      </typ:getXMLElement>[\n]"
DEBUG:>> "   </soapenv:Body>[\n]"
DEBUG:>> "</soapenv:Envelope>"
DEBUG:<< "HTTP/1.1 200 OK[\r][\n]"
DEBUG:<< "Content-Type: text/xml;charset=UTF-8[\r][\n]"
DEBUG:<< "Content-Length: 332[\r][\n]"
DEBUG:<< "Keep-Alive: timeout=5, max=100[\r][\n]"
DEBUG:<< "Connection: Keep-Alive[\r][\n]"
DEBUG:<< "[\r][\n]"
DEBUG:<< "<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><getXMLResponseElement xmlns="http://mycompany.com/types/"><result><any xmlns:ns2="http://mycompany.com/types/" xmlns="">random data</any></result></getXMLResponseElement></soap:Body></soap:Envelope>"


Another interesting note, I tried to create a new project using my localhost wsdl instead of the dev server and get this error:


Error loading [http://localhost:8080/services/MyService/webservices/myendpoint?wsdl]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA


Full error in the logs:


ERROR:com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
   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)
    at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:524)
    at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97)
    at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:236)
    at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
    at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149)
    at java.lang.Thread.run(Unknown Source)


I did a diff on the two wsdl files just to be sure and the only difference was definitely the soap:address location element.