Submit and vote on feature ideas.

Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

gsoap header generation => wsdl mismatch

Options
LegacyForum
LegacyForum Posts: 1,664 ✭✭
edited December 2016 in SOAtest
Hello,

Below are 2 links to other people's issues. What they are experiencing is similar to what is going on for me.
Especially the one with: error with several namespaces in the same apache server

Re: error with several namespaces in the same apache server
http://markmail.org/message/m64hid2mhi6c3h...v+state:results

Re: wsdl -> .h -> gsoap = namespace mismatch ?
https://www.x.com/message/75966?tstart=0

Even though I have "ns" in the header file, I get "tns" in the .wsdl file which is causing problems.

In the header file, I have
----------------------------------------------------------------------------------
//gsoap ns service name: condime
//gsoap ns service style: rpc
//gsoap ns service encoding: encoded
//gsoap ns service namespace: http://simba/condime.wsdl
//gsoap ns service location: http://simba:8600/DimeServer
//gsoap ns schema namespace: urn:condime


---------------------------------------------------------------------------------

ALL of the functions in the file defined with: "ns__XXXX"

example:
int ns__specialGetImageServer(
xsd__string original_host_name,
xsd__int original_port,
xsd__string target_name,
xsd__int target_type,
xsd__double original_file_id,
xsd__int *retval );




When I run the code generated, I get the following in the RECV.log:

-------------------------------------------------------------------------------------
HTTP/1.1 500 Internal Server Error
Server: gSOAP/2.7
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: close

264
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/&quot; xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd="http://www.w3.org/2001/XMLSchema&quot; xmlns:ns="urn:condime"><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>Method 'ns:specialGetImageServerResponse' not implemented: method name or namespace not recognized</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
0
--------------------------------------------------------------------------------

When I do a grep on the WSDL file generated, I see the following:

Again: the main thing is : ns:specialGetImageServerResponse' not implemented: method name or namespace not recognized

When I go through the .wsdl file, I see that specialGetImageServer

is defined WITH => "tns:specialGetImageServerResponse"

and NOT => "ns:specialGetImageServerResponse"



--------------------------------------------------------------------------------

grep specialGetImageServer *.wsdl
<message name="specialGetImageServerRequest">
<message name="specialGetImageServerResponse">
<operation name="specialGetImageServer">
<documentation>Service definition of function ns__specialGetImageServer</documentation>
<input message="tns:specialGetImageServerRequest"/>
<output message="tns:specialGetImageServerResponse"/>
<operation name="specialGetImageServer">
--------------------------------------------------------------------------------


QUESTION: WHY is there a MISMATCH between what is specified in the HEADER file and the generated .wsdl??

TIA
Tagged:

Comments

  • LegacyForum
    LegacyForum Posts: 1,664 ✭✭
    edited January 2011
    Options
    Hello NiteRider,

    Thank you for your question.

    This sounds like an issue that is very specific to your environment. The Parasoft forum is for self-support and is not an official Parasoft support channel.

    Please contact the official SOAtest support line at soatestsupport@parasoft.com or (888) 305-0041 for further assistance.

    Regards,
    Adam

Tagged