[erlang-questions] Erlang, WSDL, SOAP.
Tue Apr 29 17:00:19 CEST 2014
Been using erlsom+detergent for a couple of years now. A heavily modified
version of detergent that is. We also experienced lots of pain, especially
with more complicated WSDLs.
Our use case was Google's AdWords API, which we got to work with detergent,
with a lot of adhoc-solutions for different clashes between the services.
When we also tried to implement BING Ads Soap API with detergent we got
completely stuck, we couldn't get it to work at all, which is a shame.
In the end we wrote our own tool called ews (erlang web services) which is
about to enter production soon:ish. It handles all services i have thrown
at it so far (around 30:ish). We do plan to opensource it at a time when we
feel it is getting stable and feature complete.
Generating well-spec:ed functions for all service operations is not yet
implemented, but is on our todo-list. Since we are stuck with soap for the
foreseeable future, I don't see us stop supporting this tool, and hopefully
it can be something others might want to consider when working with SOAP.
On Tue, Apr 29, 2014 at 4:09 PM, Thomas Elsgaard
> On Tue, Apr 29, 2014 at 11:48 AM, Max Lapshin <max.lapshin@REDACTED>wrote:
>> I'm writing Onvif implementation in Erlang and I experience pain (no,
>> wrong, it is PAIN) with handling all that nice XML, XPath, SOAP, WSDL
>> stuff with ad-hoc self-written implementations.
>> I have a very serious feeling that it is possible to write a generator of
>> boiler plate code that will translate funcall to SOAP XML packet and back.
>> I've looked at this: https://github.com/campanja/detergent and haven't
>> found there authorization and exact routing code.
>> Am I the only one who is suffering from this?
>> Right now I need working soap client and later soap server.
>> erlang-questions mailing list
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions