xml-rpc-api2cpp(1) [centos man page]
XML-RPC-API2CPP(1) General Commands Manual XML-RPC-API2CPP(1) NAME
xml-rpc-api2cpp - Make a C++ wrapper class for an XML-RPC API SYNOPSIS
xml-rpc-api2cpp server-url remote-method-prefix c++-class-name DESCRIPTION
xml-rpc-api2cpp queries an XML-RPC server using the XML-RPC Instrospection API designed by Edd Dumbill. It then prints a C++ wrapper class to standard output. This class can be used with xmlrpc-c's C++ API. You can find a list of supported XML-RPC server libraries (and patches for many others) at http://xmlrpc-c.sourceforge.net/hacks.php. OPTIONS
server-url The name of the server to query. Try http://xmlrpc-c.sourceforge.net/cgi-bin/interop.cgi. remote-method-prefix The prefix of the methods to wrap. For example, to wrap all the system.* calls, you could specify "system". c++-class-name The name of the C++ class to generate. Try "SystemProxy". BUGS
xml-rpc-api2cpp can't talk to certain PHP servers based on Edd Dumbill's PHP library, because the trailing bytes of the XML-RPC message get truncated in HTTP pipelining mode. It's not clear whether this is a PHP, Apache or w3c-libwww bug. xml-rpc-api2cpp assumes that method descriptions are ASCII text, not HTML as specified in the standard. (In practice, both conventions are often seen.) It may also get unhappy if method descriptions contain "*/". In general, error messages and diagnostics are still fairly poor. SEE ALSO
xmlrpc-c(7), xml-rpc-api2txt(1). This program is part of xmlrpc-c. AUTHOR
This manual page was written by Eric Kidd <eric.kidd@pobox.com>. It may be distributed under the same terms as the rest of xmlrpc-c. June 27, 2001 XML-RPC-API2CPP(1)
Check Out this Related Man Page
RPC::XML::ParserFactory(3pm) User Contributed Perl Documentation RPC::XML::ParserFactory(3pm) NAME
RPC::XML::ParserFactory - A factory class for RPC::XML::Parser objects SYNOPSIS
use RPC::XML::ParserFactory; ... $P = RPC::XML::ParserFactory->new(); $P->parse($message); DESCRIPTION
The RPC::XML::ParserFactory class encapsulates the process of creating parser objects that adhere to the interface described in RPC::XML::Parser. Under the hood, the parser object created and returned could be from any of a number of implementation classes. IMPORT-TIME ARGUMENTS You can specify a particular underlying parser class to use, if you do not want RPC::XML::ParserFactory to use the default class. This is done with the "class" keyword: use RPC::XML::ParserFactory (class => 'XML::Parser'); The value may be the name for any of the built-in classes, or it may be the name of a class that inherits from RPC::XML::Parser (and can thus be "manufactured" by the factory). The value is saved and becomes the default class for any calls to new that do not explicitly name a class to use. Note that if the specified class is not valid, this is not tested until the first call to new, at which point an invalid class will cause an exception (error) to occur. The constructor will return "undef" and the $RPC::XML::ERROR variable will contain the error message. Names of Built-In Parsers The following names are valid when specified as the value of the "class" argument described above: XML::Parser xml::parser xmlparser All of these specify the parser implementation based on the XML::Parser module. This is the default parser if the user does not specify any alternative. XML::LibXML xml::libxml xmllibxml These specify a parser implementation based on the XML::LibXML module. This is a new parser and not as well-vetted as the previous one, hence it must be explicitly requested. SUBROUTINES
/METHODS The methods are: new([ARGS]) Create a new instance of the class. Any extra data passed to the constructor is taken as key/value pairs (not a hash reference) and attached to the object. This method passes all arguments on to the new() method of the chosen implementation class, except for the following: class NAME If the user chooses, they may specify an explicit class to use for parsers when calling new(). If passed, this overrides any value that was given at use-time (processed by import()). DIAGNOSTICS
The constructor returns "undef" upon failure, with the error message available in the global variable $RPC::XML::ERROR. BUGS
Please report any bugs or feature requests to "bug-rpc-xml at rt.cpan.org", or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=RPC-XML <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=RPC-XML>. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes. SUPPORT
o RT: CPAN's request tracker http://rt.cpan.org/NoAuth/Bugs.html?Dist=RPC-XML <http://rt.cpan.org/NoAuth/Bugs.html?Dist=RPC-XML> o AnnoCPAN: Annotated CPAN documentation http://annocpan.org/dist/RPC-XML <http://annocpan.org/dist/RPC-XML> o CPAN Ratings http://cpanratings.perl.org/d/RPC-XML <http://cpanratings.perl.org/d/RPC-XML> o Search CPAN http://search.cpan.org/dist/RPC-XML <http://search.cpan.org/dist/RPC-XML> o MetaCPAN https://metacpan.org/release/RPC-XML <https://metacpan.org/release/RPC-XML> o Source code on GitHub http://github.com/rjray/rpc-xml <http://github.com/rjray/rpc-xml> LICENSE AND COPYRIGHT
This file and the code within are copyright (c) 2011 by Randy J. Ray. Copying and distribution are permitted under the terms of the Artistic License 2.0 (http://www.opensource.org/licenses/artistic-license-2.0.php <http://www.opensource.org/licenses/artistic-license-2.0.php>) or the GNU LGPL 2.1 (http://www.opensource.org/licenses/lgpl-2.1.php <http://www.opensource.org/licenses/lgpl-2.1.php>). CREDITS
The XML-RPC standard is Copyright (c) 1998-2001, UserLand Software, Inc. See <http://www.xmlrpc.com> for more information about the XML- RPC specification. SEE ALSO
RPC::XML, RPC::XML::Client, RPC::XML::Server, XML::Parser AUTHOR
Randy J. Ray "<rjray@blackperl.com>" perl v5.14.2 2011-07-23 RPC::XML::ParserFactory(3pm)