Data Service & soapUI

Anonymous · ‎2011-06-27

Hi guys,
I'm trying to test a Data Service from soapUI and it seems that the generated WSDL is malformed :
ERROR:javax.wsdl.WSDLException: WSDLException (at /HTML): faultCode=INVALID_WSDL: Expected element '{http://schemas.xmlsoap.org/wsdl/}definitions'.
My data service is quite simple :
tESBProdiverRequest --> tESBProdiverResponse
All default component parameters, nothing configure..
Thanks,
Bahaaldine

Anonymous · ‎2011-06-27

That's interesting, can you attach the WSDL generated by Data Service.
Where do you run your service in Studio or in the Runtime?
Please make sure you see the WSDL by the URL you give in the SOAP UI.

Anonymous · ‎2011-06-27

Hi Renat,
I run the service directly in the studio and
I see the WSDL when I copy & paste the URL in my web browser.
Below the generated WSDL.


<DEFINITIONS WSDL="http://schemas.xmlsoap.org/wsdl/" name="LOCALPROJECT_ProviderJobFirstRequestResponse" targetnamespace="http://talend.org/esb/service/job">
<TYPES>
<SCHEMA XSD="http://www.w3.org/2001/XMLSchema" attributeformdefault="unqualified" elementformdefault="qualified" targetnamespace="http://talend.org/esb/service/job">
<ELEMENT name="invokeInput" nillable="true" type="xsd:anyType"></ELEMENT>
<ELEMENT name="invokeOutput" nillable="true" type="xsd:anyType"></ELEMENT>
</SCHEMA>
</TYPES>
<MESSAGE name="invoke">
<PART element="tns:invokeInput" name="request"></PART>
</MESSAGE>
<MESSAGE name="invokeResponse">
<PART element="tns:invokeOutput" name="response"></PART>
</MESSAGE>
<PORTTYPE name="LOCALPROJECT_ProviderJobFirstRequestResponse">
<OPERATION name="invoke">
<INPUT message="tns:invoke" name="invoke" />
<OUTPUT message="tns:invokeResponse" name="invokeResponse"></OUTPUT>
</OPERATION>
</PORTTYPE>
<BINDING name="LOCALPROJECT_ProviderJobFirstRequestResponseSoapBinding" type="tns:LOCALPROJECT_ProviderJobFirstRequestResponse">
<BINDING SOAP="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http"></BINDING>
<OPERATION name="invoke">
<OPERATION SOAP="http://schemas.xmlsoap.org/wsdl/soap/" soapaction="http://talend.org/esb/service/job/invoke" style="document"></OPERATION>
<INPUT name="invoke">
<BODY SOAP="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"></BODY>
</INPUT>
<OUTPUT name="invokeResponse">
<BODY SOAP="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"></BODY>
</OUTPUT>
</OPERATION>
</BINDING>
<SERVICE name="LOCALPROJECT_ProviderJobFirstRequestResponse">
<PORT binding="tns:LOCALPROJECT_ProviderJobFirstRequestResponseSoapBinding" name="LOCALPROJECT_ProviderJobFirstRequestResponse_Port">
<ADDRESS SOAP="http://schemas.xmlsoap.org/wsdl/soap/" location="http://127.0.0.1:8088/esb/provider"></ADDRESS>
</PORT>
</SERVICE>
</DEFINITIONS>

Anonymous · ‎2011-06-27

BTW, there is also a missing namespace alias (for the targetNamespace) in the generated WSDL :

The namespace for alias "tns" is not defined.

Anonymous · ‎2011-06-27

That's very strange. In your first post SOAPUI were not able to find '{http://schemas.xmlsoap.org/wsdl/}definitions'' which is a root WSDL element. It was apparently getting an HTML response from the server (404?). I was able to reproduce the missing namespace issue, however it is not the issue you have, could you please recheck and post the exception from the SOAPUI again?

Anonymous · ‎2011-06-27

Ok I think that we can forget the first issue because it was due to my customer network ...
But as you saw the namespace issue is still there

Anonymous · ‎2011-06-27

Yup. Good that you found it! I created a JIRA: https://jira.sopera.de/browse/TESB-2125 I still have a feeling that undeclared namespace prefix in the name of the operation does not disturb anyone, I mean SOAPUI works with it, as well as CXF consumers. It just don't feel right but in practice still works. Going to fix it anyway.

Java

Other

SOAP

XML