# Copyrights 2007-2009 by Mark Overmeer. # For other contributors see ChangeLog. # See the manual pages for details on the licensing terms. # Pod stripped from pm file by OODoc 1.06. # This pm file demonstrates how a client-side and server-side definition # of a message can be created, in case there is no WSDL for the SOAP # interface. This same module is used in both client.pl and server.pl. package MyExampleCalls; use vars '$VERSION'; $VERSION = '2.01'; use base qw/Exporter/; use XML::Compile::Util qw/pack_type SCHEMA2001/; our @EXPORT = qw/ @my_additional_schemas @get_name_count_input @get_name_count_output /; # You may have some types you need to load as well. You can use filenames # or strings, or... anything XML::Compile::dataToXML() accepts. my $myns = 'http://my-test-ns'; my $schemans = SCHEMA2001; our @my_additional_schemas = ( <<__XML ); __XML # WSDL term 'input' means: input for the server; the request which the # client will sends to the server. # In this example, the lines which define the message --to be specified # with method XML::Compile::SOAP::compileMessage()-- are listed. our @get_name_count_input = ( body => [ request => pack_type($myns, 'getNameCount') ] ); # WSDL term 'output': send by the server, as response to the client's # request. our @get_name_count_output = ( body => [ answer => pack_type($myns, 'getNameCountResponse') ] ); 1;