[erlang-questions] Erlang, WSDL, SOAP.

Andreas Schultz aschultz@REDACTED
Mon May 5 12:44:18 CEST 2014


I haven't done anything with WDSL (yet), but what about the WSDL/SOAP support
in yaws?


----- Original Message -----
> Hi Christy,
> That's pretty good advice for creating new web services. But then every
> implementation then becomes a new, custom design task. I was proposing that
> solving those two infrastructural problems (xmlns/xs) in a more generic way
> could make interoperability a little easier. I'd really like to "black box"
> the xml part into some standard transformation/codec and then largely forget
> about the details. That could I think do most of the heavy lifting with
> respect to creating direct replacements for existing services or creating
> clients to integrate with existing ones.
> It's certainly possible that I'm wrong about this. I suspect that java
> bindings end up looking like a mess because the data structures produced by
> xml are kind of inherently messy and over-complex already... so maybe any
> effort to create bindings is going to end up a mess?
> Regards,
> Steve
> On Friday, May 2, 2014 10:02:27 AM UTC-5, Christy Watson wrote:
> I'm an erlang newbe, but even with java ee and code generation based on
> a wsdl. The actual mapping to the objects must be done by the
> programmer, and is a mess. The wsdl concept is great, I just think the
> standard is to overly complicate the implementation. Remember all a
> wsdl is for is to say to the user of the service "if you send me
> __________ I'll send you ____________ back". So others have
> auto-generated themselves into a mess. Ask yourself what you really
> need to do to get from input to output, then map your algorithm...
> you'll probably end up with a much more efficient piece of software than
> an auto-generated jaxWS mess.
> On 04/30/2014 08:17 PM, Steve Davis wrote:
> > has been that the issues surrounding web services are not the WSDL but
> > resolving other technologies that it uses: i.e. the resolution of
> > namespace mapping and schema analysis.
> > 
> > 1) It's pretty obvious that namespaces (aka packages, etc) introduce
> > many indirection concerns (consider the earlier experiment in erlang
> > with module "packages").
> > 
> > 2) The issue with xml schema seems to be the underlying DTD
> _______________________________________________
> erlang-questions mailing list
> erlang-q...@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

Dipl. Inform.
Andreas Schultz

email: as@REDACTED
phone: +49-391-819099-224
mobil: +49-170-2226073

------------------- enabling your networks -------------------

Travelping GmbH               phone:         +49-391-819099229
Roentgenstr. 13               fax:           +49-391-819099299
D-39108 Magdeburg             email:       info@REDACTED
GERMANY                       web:   http://www.travelping.com

Company Registration: Amtsgericht Stendal Reg No.:   HRB 10578
Geschaeftsfuehrer: Holger Winkelmann | VAT ID No.: DE236673780

More information about the erlang-questions mailing list