dolavoie has asked for the wisdom of the Perl Monks concerning the following question:
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Help getting started with SOAP
by tachyon-II (Chaplain) on May 28, 2008 at 17:56 UTC | |
| [reply] | |
by Your Mother (Archbishop) on May 28, 2008 at 21:42 UTC | |
See also, XML::Compile::SOAP and family. | [reply] |
|
Re: Help getting started with SOAP
by skirnir (Monk) on May 28, 2008 at 18:35 UTC | |
| [reply] |
by psini (Deacon) on May 28, 2008 at 18:46 UTC | |
I stopped before answering you thar SOAP::Lite sucks, and went and see on cpan. When I tried and use SOAP::Lite in 2001 it was painfully incomplete (and inchoerent) with only a partial implementation of soap 1.1 and some quirks that costed me a week of debugging... Now it seems a much more mature object and if you have used it I'll really appreciate a valutation of its stability/features. Rule One: Do not act incautiously when confronting a little bald wrinkly smiling man. | [reply] |
|
Re: Help getting started with SOAP
by psini (Deacon) on May 28, 2008 at 18:35 UTC | |
SOAP is not difficult to understand if you already know how to use XML. In short a SOAP web service works as follows The connection is really an HTTP connection in which you have to specify an URL (composed by address of server and name of the service you require) and a XML namespace. Both URL and namespace are application dependant so you should get them from the service provider. The request and response streams are XML files, using the specified namespace, and contain the data you are exchanging with the server. The structure of request and response streams are usually described in a WSDL document which is a XML schema document. WSDL too shoud be obtained from the service provider, as it completely describe the service itself. Rule One: Do not act incautiously when confronting a little bald wrinkly smiling man. | [reply] |
by dolavoie (Initiate) on May 29, 2008 at 12:30 UTC | |
| [reply] [d/l] |
by psini (Deacon) on May 29, 2008 at 13:10 UTC | |
I should say so. Some points: You could use SOAP::Lite module, which act as a wrapper around HTTP and SOAP protocols and can simplify the last part of the script. As I said earlier I personally don't use this module since 2002, so I can't be of much help here You should use a XML serializer to build the request packet (I myself use XML::Writer) so that it is its responsability ensure the syntactical correctness of the XML stream (tag matching, escaping, an so on) You said that your service require authentication, but I can't see a header tag in your envelope... Rule One: Do not act incautiously when confronting a little bald wrinkly smiling man. | [reply] |