Invalid WSDL generation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ladon |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
I'm unable to get complex types working with SUDS SOAP client. I'm even unable to return an array (python list), always getting this error:
suds.TypeNotFound: Type not found: 'item'
XML:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://
Is it really supposed to work ? I failed to find any client which is working with Ladon :(
Changed in ladon: | |
status: | Confirmed → Fix Committed |
Thanks for this report.
The bug turned out to be related with the wsdl generation and not the response object.
When defining LadonType classes with "_" in the class name, the wsdl generator replaced "_" with "-" for ComplexType attribute "name". Then later in the wsdl file when the ComplexType was to be used as element type the replacement was not done. The effect was orphaned ComplexTypes and element references to non-existing complex types.
The very simple bug-fix is attached to this bug.