Here's an example that uses SOAP::Lite. The following code creates a SOAP::Lite object and uses it, but what's special about the SOAP::Lite object is that it's based on code that lives on www.soaplite.com. In other words, the code that lives on the remote end of the connection might not be Perl at all—but by using SOAP::Lite, you can execute the f2c( ) function as if you were calling f2c( ) from your own Perl program.

#!/usr/local/bin/perl -w

use SOAP::Transport::HTTP;

SOAP::Transport::HTTP::CGI
    -> dispatch_to('Hello::(?:hello)')
    -> handle
    ;

This example has two key parts: it will look for a module named "Hello" and will execute Hello::hello( ) when called. Note that you don't have to explicitly "require" Hello.pm; SOAP::Lite does this for you. Now, let's look at the client:

#!/usr/local/bin/perl -w

use SOAP::Lite;

# If you want to see why something isn't working, enable +trace after
# use SOAP::Lite, as shown below     

#use SOAP::Lite +trace;
    
my $proxy = 'http://www.some.server/cgi-bin/hello';
    
print SOAP::Lite
    -> uri('urn:Hello')
    -> proxy($proxy)
    -> hello()
    -> result . "\n\n"
    ;

It's essential that uri, as used above, matches the module in which the hello( ) function lives. If it doesn't, you won't see any returned results, since SOAP::Lite won't be able to find the module in @INC (using the +trace option makes it clear that an unavailable module was not found in @INC). Now that we have some context, let's take a look at the proxy option. In the above example, proxy is the URL where the SOAP server lives. When SOAP::Lite sees the proxy option, it loads the appropriate module based on what you request.