running wsdl2py -f <filename> returns no error but generates an empty Locator class for the service; the file looks 'truncated', i.e. the generated class does not even contain a 'pass' statement:
# Locator
class SimpleTestServiceLocator:
If the wsdl contains (note the trailing '/' after 'soap')
Hmm... I don't see a trailing '/' in the second example. However, this is the error. The namespace is documented (with the traling slash) here: http://www.w3.org/TR/wsdl#_notational
Namespaces are just strings (not urls), so it needs to be exact.
Good Luck, Tim.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Experimenting with the wsdl2py tool, I noticed a strange behavior with the xmlns attributes.
If my wsdl contains something like the following:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions ...
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap"
...>
running wsdl2py -f <filename> returns no error but generates an empty Locator class for the service; the file looks 'truncated', i.e. the generated class does not even contain a 'pass' statement:
# Locator
class SimpleTestServiceLocator:
If the wsdl contains (note the trailing '/' after 'soap')
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions ...
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap"
...>
then the tool works correctly.
Is this a known problem? Am I getting something wrong?
Thanks,
Paolo
Hmm... I don't see a trailing '/' in the second example. However, this is the error. The namespace is documented (with the traling slash) here: http://www.w3.org/TR/wsdl#_notational
Namespaces are just strings (not urls), so it needs to be exact.
Good Luck, Tim.