From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Subject: Re: SOAP, WSDL
Date: Mon, 09 Feb 2015 19:38:45 +0100 [thread overview]
Message-ID: <87386fq6a2.fsf@gmx.de> (raw)
In-Reply-To: <87egpzdmpb.fsf_-_@violet.siamics.net> (Ivan Shmakov's message of "Mon, 09 Feb 2015 17:22:24 +0000")
Ivan Shmakov <ivan@siamics.net> writes:
> … Which brings this long unasked question of mine: why can’t we
> just have soap-lite.el, too? And thus cease to bother about
> either Debbugs.wsdl, /or/ WSDL support in soap-client.el in
> general – in the cases the service at hand doesn’t happen to
> provide a ready to use WSDL file.
Most of the SOAP services I know offer an WSDL file. soap-client.el
gives you full support for that.
For debbugs a soap-lite.el package would have helped me three years ago,
but this is old history.
> (I’m not a SOAP expert, but I’ve got an impression that WSDL is
> an entirely separate layer used over “plain” SOAP.)
Well, looking at very complex WSDL files I believe it helps to
understand and implement the API details. With the experience of
debbugs, I believe it would have been more simple to implement it with
an existing WSDL file. Debugging Debbugs::SOAP (the Perl module from the
BTS team) was not simple as I hoped.
Something like soap-lite (be it Perl or Lisp) is easy to use for the
guys offering a service, as it has been for the BTS team. They know what
is behind. If you are just a "consumer" of an API, WSDL is more useful
for understanding.
Best regards, Michael.
next prev parent reply other threads:[~2015-02-09 18:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 21:21 [elpa] Excorporate: Exchange integration package Thomas Fitzsimmons
2015-02-09 4:08 ` Stefan Monnier
2015-02-09 6:56 ` Achim Gratz
2015-02-09 8:05 ` Michael Albinus
2015-02-09 9:05 ` joakim
2015-02-09 11:00 ` Daniel Colascione
2015-02-09 12:24 ` Thomas Fitzsimmons
2015-02-09 12:40 ` David Kastrup
2015-02-09 14:16 ` Stefan Monnier
2015-02-10 20:23 ` Stefan Monnier
2015-02-11 1:24 ` Thomas Fitzsimmons
2015-02-11 6:55 ` Tassilo Horn
2015-02-11 9:42 ` David Kastrup
2015-02-11 12:59 ` Tassilo Horn
2015-02-11 13:07 ` Dmitry Gutov
2015-02-11 13:53 ` Michael Albinus
2015-02-11 15:01 ` Tassilo Horn
2015-02-09 22:07 ` Richard Stallman
2015-02-09 8:14 ` Michael Albinus
2015-02-09 12:41 ` Thomas Fitzsimmons
2015-02-09 13:02 ` Michael Albinus
2015-02-09 13:21 ` Thomas Fitzsimmons
2015-02-09 13:34 ` Michael Albinus
2015-02-09 17:22 ` SOAP, WSDL Ivan Shmakov
2015-02-09 18:38 ` Michael Albinus [this message]
2015-02-09 18:50 ` Ivan Shmakov
2015-02-09 14:09 ` [elpa] Excorporate: Exchange integration package Stefan Monnier
2015-02-09 10:06 ` SAKURAI Masashi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87386fq6a2.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).