Round trips through the code generation and back to the WSDL are inconsistent.
<wsdl:service name="PutOps">
<wsdl:port name="PutOpsPort" binding="tns:PutOpsBinding">
<!-- ... --->
</wsdl:port>
</wsdl:service>
put through code generation becomes:
PutOpsPort_SERVICE = soap.Service(
name='PutOpsPortType',
...
)
which going back incorrectly becomes:
<wsdl:service name="PutOpsPort">
<wsdl:port name="PutOpsPortPort" binding="tns:PutOpsPortBinding">
<!-- ... --->
</wsdl:port>
</wsdl:service>
...and so on...
Also of note is that soapfish.py2wsdl expects SERVICE which isn't available without editing the name of PutOpsPort_SERVICE.
I've put this into the 0.7.0 milestone as whatever fix we come up with will be a breaking change and also because I'm not yet sure how this should be solved.
Round trips through the code generation and back to the WSDL are inconsistent.
put through code generation becomes:
which going back incorrectly becomes:
...and so on...
Also of note is that
soapfish.py2wsdlexpectsSERVICEwhich isn't available without editing the name ofPutOpsPort_SERVICE.I've put this into the 0.7.0 milestone as whatever fix we come up with will be a breaking change and also because I'm not yet sure how this should be solved.