In most projects, we seem to be making some kind of consumption of SOAP web services. And each time it seems that he repeatedly hits the head with a brick. For example, we get:
- Dozens of classes that our developers barely understand.
- Awkward API (especially when using .NET web services).
- It’s hacking into what we usually generate from a local WSDL file (a remote service rarely exists at the start of development).
In Python, I used Suds (https://fedorahosted.org/suds), which provides a truly natural (but obviously less secure type) API. I know this is a comparison of apples and oranges, but there is a less painful way to call a remote web service than to generate so much code.
Most likely, we will use this in the Play structure, although, if possible, I will like something in common. We also use Spring a lot, although I am currently looking at Guice for a simpler alternative.
Martin
java soap web-services
optilude
source share