I'm still not clear on where SOAP::Lite finds what names/methods are available on the remote server.
Believe it or not -- it doesn't.
It's up to the programmer to know what the methods are. There are structured ways of representing this information, for those people who use code generators, using WSDL (which I consider to be the bane of my existance]
Some SOAP toolkits will return a wsdl if you attempt to GET the proxy URL with a QUERY string of 'wsdl'.... so in your example, you could try pointing a web browser at:
http://services.soaplite.com/hibye.cgi?wsdl(it won't actually work, though, because SOAP::Lite doesn't support this by default, as it doesn't generate WSDL -- you're left to do that on your own)
Now -- you're probably going to ask how autodispatch works then ... well, it just assumes that if it sees a command that it doesn't know about, then it should try the SOAP service.
In reply to Re: Syntax used by SOAP::Lite
by jhourcle
in thread Syntax used by SOAP::Lite
by smeenz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |