interoperability with WCF service about soapfish HOT 5 CLOSED

can you provide some python sample code so we can reproduce the issue ourself? Ideally we'd have a simple python test case which contains your (minimal) model, the expected output as well as the current output.

That being said missing namespaces should be fixable.

from soapfish.

I created repo with sample code:
https://github.com/sergey-aleshin/soaptest

See test.py and wcf.soap.xml files.

client.py was generated by wsdl2py from http://seweb.bars-glonass.ru/seweb5wcf/Service.svc?wsdl

wcf.soap.xml was produced by WCF Test Client for AddContract method

The main diffrence between xml produced by soapbox-bsd and wcf test client is use of d4p1 namespace. Without this namespace wcf service can not parse request properly and all fields of CI parameter are nulls.

from soapfish.

Hi,

I did not have the time to investigate your problem yet, but I encountered a similar issue with namespaces. You might try this commit trecouvr/soapbox-bsd@3355d64 from my branch wich is not yet merged in Felix's repo.

from soapfish.

I just checked the requests produced by your test.py file with the latest soapfish code and it generates the same SOAP requests as FlightDataServices/soapbox@78a59005dfda481fcbbbbecdccffec627a341372 .

For the record: These are the SOAP bodies which are generated currently:

<ns0:Envelope xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/">
  <ns0:Body>
    <ns0:AddContract xmlns:ns0="http://tempuri.org/">
      <ns0:CI>
        <ns0:Login xmlns:ns0="http://schemas.datacontract.org/2004/07/">asg6</ns0:Login>
        <ns0:Password xmlns:ns0="http://schemas.datacontract.org/2004/07/">1234</ns0:Password>
      </ns0:CI>
    </ns0:AddContract>
  </ns0:Body>
</ns0:Envelope>

# --- second request -------------------------------------------------------------------
<ns0:Envelope xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/">
  <ns0:Body>
    <ns0:GetNewSessionId xmlns:ns0="http://tempuri.org/">
      <ns0:UserLogin>asg6</ns0:UserLogin>
      <ns0:UserPassword>1234</ns0:UserPassword>
    </ns0:GetNewSessionId>
  </ns0:Body>
</ns0:Envelope>

However I'm not completely sure that we generate bad SOAP requests in the first place. It is confusing for sure that the "ns0" namespace is redefined so often but as far as I can see the CI tag is in the http://tempuri.org/ namespace while Login and Password are using http://schemas.datacontract.org/2004/07/.

Also the server seems to be happy about the XML we're sending. The answer I got for the first request uses HTTP status code 200 and does not contain any Faults:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Body>
    <AddContractResponse xmlns="http://tempuri.org/">
      <AddContractResult>bbb7c6b6-c730-493b-90f0-ebeacba89977</AddContractResult>
    </AddContractResponse>
  </s:Body>
</s:Envelope>

@sergey-aleshin If I'm right, we could close this ticket as there is nothing wrong with the code, right? Maybe everything works as expected already?

I understand that is has been a long time since you filed that ticket. Sorry for the late response. In case you solved that problem and/or moved on please leave a short notice so we can close that ticket. I'm trying to keep the only "active" issue in the tracker so I'd like to avoid "stale" tickets :-)

from soapfish.

I'm closing this ticket as I think there is nothing to do for soapfish. Feel free to reopen in case I'm wrong (I'll be happy to help). Thank you very much for your effort reporting this issue.

from soapfish.