Named XSD Element with unnamed complexType child generates invalid python. about soapfish HOT 4 OPEN

@techdragon: Could you attach a full *.xsd and *.wsdl? Also if you could submit a pull request, then I can see what changes you are trying to make and better understand the problem. Thanks.

@oskrkal: Just been made aware of your fork. Were you planning to submit a pull request for your fixes? Or are you happy for me to pull in some of the changes?

from soapfish.

This is the diff: https://github.com/FlightDataServices/soapfish/compare/95f902d9d4e848034946ed0f56b450b9b7c4d28c...oskrkal:references

It's a lot of changes.

from soapfish.

@pope1ni I'm not able to submit the actual WSDL and XSD files, corporate confidentiality reasons. I'll try and make a minimal test case XSD & WSDL at work tomorrow, worst case I can post the full XSD & WSDL after I sanitise them. I'll also make a pull request so you can see the changes.

@pope1ni If I'm going to add some test coverage for the pull request... would it be better to modify one of the existing tests/assets/generation/*.wsdl files to cover the 'test case' in the wsdl, or create a new test with its own separate wsdl file?

from soapfish.

Thanks. A minimal test case would be useful. I'd add separate test resources for now. We can always combine them later if it makes sense.

from soapfish.