Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Round trip through wsdl2py and py2wsdl should be consistent. #103

Open
ngnpope opened this issue May 8, 2017 · 0 comments
Open

Round trip through wsdl2py and py2wsdl should be consistent. #103

ngnpope opened this issue May 8, 2017 · 0 comments

Comments

@ngnpope
Copy link
Member

ngnpope commented May 8, 2017

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.

@ngnpope ngnpope added this to the 0.7.0 milestone May 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant