Home >> All >> org >> apache >> [ xmlrpc Javadoc ]

•	org.apache.xmlrpc.applet.* (5)	•	org.apache.xmlrpc.fesi.* (3)
•	org.apache.xmlrpc.secure.* (5)	•	org.apache.xmlrpc.secure.sunssl.* (1)
•	org.apache.xmlrpc.util.* (2)

• org.apache.xmlrpc: Javadoc index of package org.apache.xmlrpc.


Package Samples:

• org.apache.xmlrpc.fesi
• org.apache.xmlrpc.util
• org.apache.xmlrpc.applet
• org.apache.xmlrpc.secure
• org.apache.xmlrpc.secure.sunssl

Classes:

• JSXmlRpcApplet: An applet that can be accessed via LiveConnect from JavaScript. It provides methods for adding arguments and triggering method execution for XML-RPC requests. This works on recent Netscape 4.x browsers as well as Internet Explorer 4.0 on Windows 95/NT, but not on IE/Mac. Results from XML-RPC calls are exposed to JavaScript as the are, i.e. <structs>s are Hashtables and <array>s are Vectors and can be accessed thru their public methods. It seems like Date objects are not converted properly between JavaScript and Java, so the dateArg methods take long values instead of Date objects as parameters ...
• FesiRpcExtension: An extension to transparently call and serve XML-RPC from the FESI EcmaScript interpreter. The extension adds constructors for XML-RPC clients and servers to the Global Object. For more information on how to use this please look at the files server.es and client.es in the src/fesi directory of the distribution. All argument conversion is done automatically. Currently the following argument and return types are supported: plain objects (with all properties returned by ESObject.getProperties ()) arrays strings date objects booleans integer and float numbers (long values are not supported!)
• DefaultTypeFactory: The default implementation of the TypeFactory interface. Provides the following mappings: XML-RPC data type Java class <i4> or <int> java.lang.Integer <boolean> java.lang.Boolean <string> java.lang.String <double> java.lang.Double <dateTime.iso8601> java.util.Date <base64> byte[ ]
• DefaultTypeDecoder: The default implementation of the TypeDecoder interface. Provides the following mappings: XML-RPC data type Java class <i4> or <int> java.lang.Integer <double> java.lang.Double, java.lang.Float
• XmlRpc: This abstract base class provides basic capabilities for XML-RPC, like parsing of parameters or encoding Java objects into XML-RPC format. Any XML parser with a SAX interface can be used. XmlRpcServer and XmlRpcClient are the classes that actually implement an XML-RPC server and client.
• XmlRpcHandler: The XML-RPC server uses this interface to call a method of an RPC handler. This should be implemented by any class that wants to directly take control when it is called over RPC. Classes not implementing this interface will be wrapped into an Invoker object that tries to find the matching method for an XML-RPC request.
• SecureWebServer: A minimal web server that exclusively handles XML-RPC requests over a secure channel. Standard security properties must be set before the SecureWebserver can be used. The SecurityTool takes care of retrieving these values, but the parent application must set the necessary values before anything will work.
• FesiRpcServer: An ESObject that makes its properties (sub-objects) callable via XML-RPC. For example, if Server is an instance of FesiRpcServer, the following would make the functions defined for someObject available to XML-RPC clients: Server.someObject = new SomeObject ();
• Base64: This class provides encode/decode for RFC 2045 Base64 as defined by RFC 2045, N. Freed and N. Borenstein. RFC 2045 : Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. Reference 1996
• XmlRpcServer: A multithreaded, reusable XML-RPC server object. The name may be misleading because this does not open any server sockets. Instead it is fed by passing an XML-RPC input stream to the execute method. If you want to open a HTTP listener, use the WebServer class instead.
• XmlWriter: A XML writer intended for single-thread usage. If you feed it a ByteArrayInputStream , it may be necessary to call writer.flush() before calling buffer.toByteArray() to get the data written to your byte buffer.
• XmlRpcClient: A multithreaded, reusable XML-RPC client object. Use this if you need a full-grown HTTP client (e.g. for Proxy and Basic Auth support). If you don't need that, XmlRpcClientLite may work better for you.
• CommonsXmlRpcTransport: Implementor of the XmlRpcTransport interface using the Apache Commons HttpClient library v2.0 available at http://jakarta.apache.org/commons/httpclient/ Note: Currently this transport is not thread safe
• SecureXmlRpcClient: A multithreaded, reusable XML-RPC client object. Use this if you need a full-grown HTTP client (e.g. for Proxy and Cookies support). If you don't need that, XmlRpcClientLite may work better for you.
• XmlRpcClientLite: A multithreaded, reusable XML-RPC client object. This version uses a homegrown HTTP client which can be quite a bit faster than java.net.URLConnection, especially when used with XmlRpc.setKeepAlive(true).
• XmlRpcClientException: This is thrown by many of the client classes if an error occured processing and XML-RPC request or response due to client side processing. This exception will wrap a cause exception in the JDK 1.4 style.
• XmlRpcException: This is thrown by the XmlRpcClient if the remote server reported an error. If something went wrong at a lower level (e.g. no http connection) an IOException will be thrown instead.
• XmlRpcException: This is thrown by the XmlRpcClient if the remote server reported an error. If something went wrong at a lower level (e.g. no http connection) an IOException will be thrown instead.
• DefaultHandlerMapping: Provide a default handler mapping, used by the XmlRpcServer. This mapping supports the special handler name "$default" that will handle otherwise unhandled requests.
• XmlRpcProxyServlet: A HttpServlet that acts as a XML-RPC proxy. The URL of the server to connect to is taken from the servlet initialization parameter url .
• XmlRpcTransportTest: Abstract Test class to be extended by the tests for each Transport. Guarantees that transports implement a base contract expected by the XmlRpcClient classes
• LiteXmlRpcTransport: Interface from XML-RPC to a 'lite' HTTP implementation. This class will use the XmlRpcClientLite.auth member for the HTTP Basic authentication string.
• XmlRpcClientResponseProcessor: Process an XML-RPC server response from a byte array or an InputStream into an Object. Optionally throw the result object if it is an exception.
• XmlRpcResponseProcessor: Process an Object and produce byte array that represents the specified encoding of the output as an XML-RPC response. This is NOT thread safe.
• XmlRpcWorker: Tie together the XmlRequestProcessor and XmlResponseProcessor to handle a request serially in a single thread.

Home | Contact Us | Privacy Policy | Terms of Service