comment on

I would do the following:

Read the SOAP::Lite documentation. (which mentions 'Limited support for WSDL schema.'
I would notice that the 'AVAILABILITY' section mentions another website (why it's not under 'SEE ALSO', I have no idea): http://soaplite.com
I would read said website, especially focusing on the Guide (such as Access with service description (WSDL)) and the Cookbook.

If I ran into a lot of trouble, I'd probably also look into SOAP::WSDL and read the WSDL spec.

I'd get very confused by it, so I'd go out and get a few books to read, such as Programming Web Services in Perl, and Programming Web Services with SOAP

I'd then get really annoyed at how interoperability among different toolkits with SOAP is a complete load of shit, and get fed up with the issues of trying to deal with complex types, and what they refer to on the SOAP Builders mailing list as 'impedence issues'.

I'd then spend a month or so digging through SOAP::Serializer (part of the SOAP::Lite module) until I understood what was going on, and write my own custom serializer.

(at least, that's what I did when I had to learn about WSDL)

Update: Minor correction -- that's not exactly what I did, because SOAP::WSDL wasn't out when I had to deal with these headaches. It's possible that it might've saved me a whole lot of time

In reply to Re: How to use SOAP::Lite with a WSDL description by jhourcle
in thread How to use SOAP::Lite with a WSDL description by Stegalex

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks