Hi.
You wrote "add this snippet in Messages.wsdl", since there
is no file
named like this, I first add it to "Messages.xsd", it didn't work, and
I switched to another tasks, thinking your fix didn't work. This
morning I add it to "Services.wsdl" and indeed it worked, I add the
list of methods. But I can't manage to get suds using my local
Services.wsdl and and talking to the exchange soap server. I'm
currently very new to soap and suds, and I would need some help. When
I change the url "suds://services.wsdl" the online wsdl, it falls back
on "no service defined". I'm sure there are options for telling suds
to connect to the server and use the local wsdl file all togethet, but
I can't spend more time on this.
Actually, if you have a correct WSDL locally, simply using that one
will fix your problem. You can do it using the DocumentStore class, as
done in existing test code, or you can store the file on disk and
reference it using the 'file://host/path' URL.
Just make sure the WSDL in question points to the correct web service
host address & port.
I took a look to the diff between suds 0.3.7 and ews-suds-0.3.7, and
the guy made an amazing work. I contacted him to ask if he was willing
to port it to the last version of suds, which I don't think he will,
and if he won't, I'll give a try to forward port the modifications to
the development version of suds. If you agree, I'll be happy to submit
the patch in order you to integrate it. Amongst those modifications,
there is one for supporting wsdl file with no wsdl:service tags.
Yeah, I also took a look at that fork, and someone did do some work
there, but the changes are not generic. E.g. the 'missing wsdl:service
tag workaround' simply fakes having such a tag by assuming it is talking
to an Exchange server - not really generic enough. I'd be happier if an
optional workaround was added that would do something like this:
1. if there are no ports defined - error out
2. if there are any ports defined - fake a service entity without a
valid host address connected to all the listed ports.
3. using such a web service would require that the client explicitly
specify the target server address before making any calls on it.
There are also some other patches there, but I do not really have any
way to test what they fix, so you'll have to take the time and do some
heavy lifting if you want such changes integrated into suds-jurko.
@Chris : i installed soapUi : it was clumsy, buggy (it considers
that
path are case insensitive by default, so it works poorly on Linux) and
very unclear. Since i could not manage to do somethinh with it in
little time, I didn't strive further).
SoapUI is a great tool on Windows. Sometimes a bit buggy/flaky, but
generally works fine.
Best regards,
Jurko Gospodnetić