Closed AlthausKonstantin closed 1 year ago
Do I have to implement the a custom class to handle the WSDL class ns4:duration (analogous to pylero.text?)
pylero.text
is tns2:Text
, it's a type which is more analogous to xsd:string
for exampleIs there some other workaround?
- I'm afraid that I don't know this
Thank you! No worries, for now I will try to talk to our repo admins maybe we can change the type on the server side. I will let you know if this fixes my problem :)
Ack, in general we might need to look into how suds map simpleType with backing base types and hack into it if possible 🤔
I was able to fix the problem by avoiding the simple types :)
Ack, in general we might need to look into how suds map simpleType with backing base types and hack into it if possible
Agreed. In my superficial research I got the impression that suds does not support simple types fully :(
Dear All,
I am running in an issue with some of my companies Polarion projects.
Here is a MWE
I have done some digging...
get_custom_fields
in this linebecauseglobals()
does not contain the key 'duration':As we get a type beginning with 'ns', pylero assumes that this type is in the global namespace. (that's what I gleaned from that code-comment) For other Polarion WSDL classes, such as the suds 'Text' from pylero.text, this is also the case.
Checking further with the suds client, I also see that the Polarion project in question has this class. This
produces the following output (here only a shortened version):
I also looked at the tracker client WSDL resources from Polarion (here) and saw that the duration type is a really simple type wich is essentially equivalent to the base type 'string'. Here is the type definition of the WSDL class:
... but here I need your input
ns4:duration
(analogous topylero.text
?)Thank you for your help!